Sign-in providers
Configure the sign-in methods available to your users.
Before you start
Use an administrator account and retain a working sign-in method. For OIDC, obtain the issuer URL, client ID, client secret, and redirect configuration from your identity provider.
Add an OIDC provider
- In the server dashboard's sidebar, open Settings → Server Settings → Auth.
- Add the provider and give it a recognizable name.
- Enter its issuer and client credentials.
- Register the displayed redirect URI at your identity provider. Leave the callback base URL override blank to use the public base URL.
- Save the provider and test sign-in in a separate browser session.
Saving performs discovery and verifies credentials when the issuer supports the corresponding grant. The login button uses the provider's configured name.
OAuth callbacks use the public base URL configured under Settings → Server Settings → Networking → Addresses. Changing that URL updates callbacks after restarting the server; register the new redirect URI with your identity provider too.
A provider's optional Callback base URL override replaces that base only for that provider. Enter a full HTTP or HTTPS origin, without a path; Subshell adds /api/auth/callback/<provider-id>. Clear the override to follow the public base URL again. The callback never comes from the hostname a visitor happens to open or from the order of an address list.
For Google, use an HTTPS hostname for a remote server. Google rejects private-IP callback URLs such as http://10.1.10.50:3080/api/auth/callback/google. The Google preset requests account selection during sign-in. See Google’s redirect URI rules for its callback requirements.
Registration and approval
Enable account creation only for providers through which you want new users to arrive. Requiring approval keeps new accounts pending until an administrator admits them.
Closing registration doesn't itself disable sign-in for existing users. The email provider's sign-in policy also governs password and passkey entry.
Preserve access
Subshell refuses a change that closes the last open sign-in provider. Successful provider changes take effect without restarting the server.
If sign-in fails, keep the existing session and inspect Sign-in and origin errors.
Next steps
Read Registration and Account recovery.
Edit on GitHubLast updated on
