If you wish, you can set up the same translate5 instance on different domains and configure for different clients different domains and different OpenID servers.
Examples how to use translate5 as OpenID client with different OpenID servers for Single-Sign-On (SSO) usage
- Google as OpenID server for translate5
- MS Azure ActiveDirectory as OpenID server for translate5
- MS ActiveDirectory Federation Services
Configuration within translate5
To configure translate5 to work with OpenId connect is very simple. Navigate to the clients tab in your translate5 instance, and under the OpenId connect fieldsub-set tab there are OpenId configuration fields that need to be set.
OpenId server: OpenId authentication server url. This is the URL translate5 redirects users for authentication at the OpenId connect server (Google configuration example:)
OpenId issuer: OpenId issuer url. In many cases this url is identical with the OPenId server url.
OpenId user name: OpenId authentication server username (Google configuration example: "Client ID" see image3)
(the user name that allows the openId client application to connect to the API of the openId server; do NOT mix this up with the username of the user, that wants to authenticate!)
Link text on login page: Label text on the login page of translate5. A click on it redirects the user to the configured openid server for authentication, instead of using translate5 for authentication. If the checbox "Do not show login page" below the field "Link text on login page" is checked, the user will directly be redirected to the openid server for authentication/authorization and will never see the translate5 login page.
Checkbox "Do not show login page: Automatically redirect to OpenID Connect server": Redirect directly to the SSO authentication provider.