Domino OIDC¶
Huddo Boards supports OIDC authentication with HCL Domino 14.5
Pre-requisites¶
- Provider configuration for more information on provider configuration.
Configuration¶
Tip
See Client registration for more information on client registration.
-
Open the
idpcat.nsfdatabase in Domino -
Click
Add OAuth Client -
Register the Huddo Boards client with the following values:
Domino OIDC provider: domidp.isw.net.au Name: Huddo Boards DEV8 Client ID: huddoboards Authentication method: Client secret basic Client secret: <generate-a-random-string-or-uuid> Redirect URI(s): https://<boards-url>/auth/dworkspace/callback Audience(s): Domino Scope(s): openid email profile Domino.user.all
Environment variables¶
Set the following environment variables in your config boards yaml file
| Key | Description |
|---|---|
user.env.DOMINO_OIDC_URL |
HCL Domino OIDC URL, e.g. https://domino.oidc.api.company.com |
user.env.DOMINO_OIDC_CLIENT_ID |
OAuth client id configured in idpcat.nsf. Default is huddoboards |
user.env.DOMINO_OIDC_CLIENT_SECRET |
OAuth client secret configured in idpcat.nsf |
user.env.DOMINO_OIDC_ISSUER |
Optional: issuer to trust, matching the iss claim in tokens from the provider. Defaults to <DOMINO_OIDC_URL>/auth/protocol/oidc. Set this only where the provider issues a different value |
user.env.DOMINO_LDAP_URL |
URL of LDAP server, e.g. ldap://ad.example.com |
user.env.DOMINO_LDAP_BIND_DN |
Bind DN for LDAP search, e.g. CN=Boards,OU=Service Accounts,DC=example,DC=com |
user.env.DOMINO_LDAP_BIND_PASSWORD |
Bind password for LDAP search |
user.env.DOMINO_LDAP_BASE_DN |
Base DN for LDAP search, e.g. DC=example,DC=com |
user.env.DOMINO_WORKSPACE_URL |
HCL Domino Workspace URL. This value is used for the Navigation header, e.g. <DOMINO_WORKSPACE_URL>/navbar/v1/component |
user.env.DOMINO_ADMINS |
Optional: Emails or GUIDs of users to grant admin permissions. |
Trusted issuer¶
Boards accepts tokens only from an issuer it has been configured with. The iss claim is compared against DOMINO_OIDC_ISSUER, or the value derived from DOMINO_OIDC_URL where that is unset, and anything else is rejected.
This matters most for OIDC Back-Channel Logout, whose endpoint is public and unauthenticated by design — the provider calls it with no user session.
Tip
A rejected token is logged as unrecognised issuer, with both the claimed and the configured value. Check that log first where logout tokens are being refused: it is the same message whether the issuer is misconfigured or the request is not from your provider.
Where a Domino OIDC client is registered in the Boards admin UI, the Domino OIDC Issuer URL field on that client takes precedence over the environment variable for tokens naming that issuer. Leave it blank unless the client's provider differs from the global one.