Registries
Bridge Registry
The Bridge Registry contains the data for one specific bridge installation.
|
Field |
Meaning |
|
UUID |
unique id of the bridge |
|
secret |
obfuscated secret |
|
gatewayId |
unique id of the gateway which this bridge will use |
|
bridgeAlias |
human readable alias to be able to reference a specific bridge on the platform side |
|
bridgeCertificate |
public certificate of the bridge |
|
platformCertificate |
public certificate of the platform |
|
versionPlatform |
aktuelle Version der Platform |
|
versionBridge |
aktuelle Version der Bridge |
Gateway Registry
The gateway registry contains all Gateways, besides the official Lobster Bridge Gatways this includes all Private Gateways on customer side.
When creating a new bridge, a check should be made to see if a DMZ is placed in front of the LDP, which automatically also becomes a gateway.
The user can choose between the DMZ (as gateway) and the default gateway. The ID of the selected gateway is reported to the API server when the bridge is created.
When the bridge is registered, the gateway checks whether it is authorized for the bridge, by checking the delivered gateway id against its own.
The host and endpoint URL of a bridge are read from the gateway registry using the gateway ID.
When a gateway boots up, it automatically registers with the gateway registry with its endpoint and host. The registry checks whether the gateway already exists and returns the ID. The provided values are also checked and updated in the registry if necessary.
getBridgeById also delivers the gatewayId
The currently marked gateway entry is the Lobster default Bridge Gateway, the other ones are private customer Bridge Gateways.
|
Field |
Meaning |
|
uuid |
unique id of the gateway |
|
gatewayBaseEndpoint |
Base endpoint URL of the gateway |
|
gatewayHost |
host:port of the gateway |