Central Logging can sign the admin in through an OpenID Connect (OIDC) provider. Once it is configured, the login page shows a Sign in with single sign-on button below the password form.
Single sign-on is another way into the same single admin account. It does not add users or roles, and it does not replace the password: the password login, and HTTP Basic Auth for curl and scripts, keep working. If the provider is down or misconfigured, log in with the password.
The provider confirms who the person is. Central Logging then decides whether to let them in. A sign-in is accepted when either:
groups claim of the ID token.If both the allowed email and the allowed group are blank, nobody can sign in with single sign-on.
Providers such as GitLab and Google let anyone create an account and finish their sign-in page. That alone never grants access: anyone who does not pass the check above is sent back to the login page with Single sign-on failed.
Single sign-on is configured on the Settings page. It is turned on when both the issuer URL and the client ID are set.
https://id.example.com, https://gitlab.com or https://accounts.google.com. Leave blank to turn single sign-on off.groups scope, so only set it with a provider that supports one (see below).Changes take effect on the next sign-in.
Every provider needs a client (sometimes called an application) for Central Logging with:
https://<host>/auth/oidc/callback, where <host> is the Host settingopenid, email and profile, plus groups if you use an allowed groupBoth your browser and the Central Logging server must be able to reach the provider over HTTPS. The server connects to it directly to read its configuration and to finish each sign-in.
Pocket ID is a self-hosted provider that signs in with passkeys.
https://<host>/auth/oidc/callback.https://id.example.com.To allow a group instead of one email, create a user group in Pocket ID, add the people who may sign in, and set OIDC Allowed Group to the group’s name as it appears in the groups claim.
Works with GitLab.com and self-managed GitLab.
https://<host>/auth/oidc/callback, check Confidential, and select the openid, profile and email scopes.https://gitlab.com, or the URL of your GitLab server.Leave OIDC Allowed Group blank. GitLab does not put group membership in the ID token claim that Central Logging reads.
https://<host>/auth/oidc/callback as an authorized redirect URI.https://accounts.google.com.Leave OIDC Allowed Group blank. Google rejects the groups scope.
GitHub is not supported. Its sign-in is plain OAuth 2.0 without OpenID Connect, so it does not issue the ID token that Central Logging verifies.
A failed sign-in shows Single sign-on failed on the login page. The reason is in the server log, on a line starting with oidc login failed: (for the systemd service, run journalctl -u centrallogging).
https://<host>/auth/oidc/callback. The log line includes the provider’s error message.email_verified=false for an address you expect to work, verify the email with the provider, or use an allowed group.Could not reach the sign-in provider means the Central Logging server could not load <issuer URL>/.well-known/openid-configuration. Check the issuer URL, and that the server can reach the provider.
To turn single sign-on off, clear OIDC Issuer URL.
💌 Get notified on new features and updates