The LinkSmart® LinkSmart Border Gateway (BGW) can authenticate and authorize access to HTTP, MQTT and WebSocket services for users defined in an OpenID Connect provider. (OIDC) provider. Simple rules providing some basic authorization (see below for details) can be maintained in the backend of the OIDC provider as user or group attributes. These rules need to be provided to BGW in the access token as a custom claim.
If anonymous access to an endpoint accessed via browser is not allowed, the Border Gateway provides the OAuth2 / OpenID Connect "Authorization Code Flow" (sometimes referred to as "Standard Flow"). You will be re-directed to your OpenID Connect provider to log in.
- User provides username/password in the REST request.
- BGW intercepts the request and negotiates with an OpenID Connect server provider for an access token. This implements the OAuth2 / OpenID Connect "Resource Owner Password Credentials Flow".
- If authenticatedthe token is valid and the authorization rules provided in the access token allow the requested resource, BGW forwards the request to the API endpoint.
Bearer token is especially useful if you are using a framework like Angular. You can set up keycloak-angular with "Standard Flow" (= "Authorization Code Flow") and connect to any REST APIs over endpoints protected by the Border Gateway. Border Gateway will validate the access token while Angular is handling login, token refresh etc.
User directly negotiates with an OpenID Connect server for an access token. Example via curl for Keycloak (OAuth2 / OpenID Connect "Resource Owner Password Credentials Flow"):
Code Block language bash
curl -d "client_id=bgw_client" -d "username=<username>" -d "password=<password>" -d "grant_type=password" "<token_endpoint_of_your_openid_connect_provider>"
- User provides the access token in the REST request to BGW.
- BGW intercepts the request and validates the access token If authenticatedand the authorization rule inside it .
- If the token is valid and the authorization rules provided in the access token allow the requested resource, BGW forwards the request to the API endpoint.
If you open an MQTT connection via the Border Gateway, you can deliver username and password as defined in the MQTT standard. Border Gateway will take these user credentials to the OpenID Connect provider and obtain an access token including the authorization rules. The token is validated and the authorization rules checked against the requested method (PUB / SUB) and topic. When the request is allowed it is forwarded to the MQTT broker.
You can also deliver an access token (as described above for HTTP) in the MQTT username field. Leave the password field empty if you do. Both types of credentials will The token will then be validated against the OpenID Connect providerand the authorization rules checked against the requested method (PUB / SUB) and topic.
By default the BGW WebSocket proxy expects that you use protocol MQTT over WebSockets so the data is forwarded to the BGW MQTT proxy and authenticated and authorized there. You can configure the WebSocket proxy to forward to any upstream server though. In this case, you need to provide your credentials in the query parameters of the URL to the WebSocket proxy. You can use either one of these two options:
let ws = new WebSocket("wss://<your_domain>:<your_port>/<your_path>?basic_auth=<base64_encoding_of_<username>:<password>>);
The LinkSmart® Border Gateway also offers some basic authorization capabilities. Authorization rules are defined as user and / or group attributes in the OpenID Connect Provider Provider´s backend (see subpage deployment).
- PROTOCOL is the transfer protocol (currently HTTP, HTTPS, MQTT or WS)
- METHOD is the method in regards to the protocol, e.g. GET,POST,DELETE for HTTP and PUB,SUB for MQTT. For WebSocket connections only CONNECT is supported.
- DOMAIN is the fully qualified domain name (FQDN)
- Case MQTT / WS: TCP port of the target / upstream service
- Case HTTPS: In In a standard deployment the BGW External Interface will add headers "x-forwarded-proto" and "x-forwarded-host" (including port) and forward to the BGW HTTP proxy so in the rules regarding HTTP services you need to use protocol HTTPS and port 443 in your rule definitions. If you deploy a BGW HTTP Proxy without the BGW External Interface, you can configure your web server (e.g. nginx) to set headers "x-forwarded-proto" and "x-forwarded-host" and define rules in the same way.
- Case HTTP: If you do not use TLS at all or cannot configure your web server to set headers "x-forwarded-proto" and "x-forwarded-host", you need to use HTTP in your rule definitions and the TCP port of BGW HTTP proxy.
- PATH is resource information and may contain slashes itself. For HTTP and WebSocket, it is the resource path (e.g. confluence/display/COM). For MQTT, it is the topic.
Loolsely based on MQTT topic specification: https://www.hivemq.com/blog/mqtt-essentials-part-5-mqtt-topics-best-practices
- Every slash adds a new section. E.g.: a/b consists of two sections and a/b/ consists of three sections last of which contains an empty string.
- Strings are case-sensitive
- A plus + is a single section wildcard. E.g.: a/+ matches a/b but not a/b/ and a/b/c
- A hash # is a multi-section wildcard and may only be used in the end. E.g.: a/# matches all a/b and a/b/ and a/b/c