Single sign-on (OIDC)
Single sign-on (SSO) lets people sign in to Tesria with an account they already have somewhere else, such as their work account, instead of a separate Tesria password. There is one password less to remember, and when someone’s work account is closed, they can no longer sign in with it here either.
Tesria works with any provider that speaks OpenID Connect (OIDC), the standard most of them use: Keycloak, Authentik, Okta, Microsoft Entra ID and Google among them. It sits alongside ordinary Tesria accounts, so nobody has to switch.
Single sign-on is in beta. It follows the OpenID Connect standard and its tests pass, but it has not yet been tried against every provider. Keep at least one ordinary administrator account with a password, so a sign-on problem never locks you out. Whether it works for you or not, please say so, naming your provider, in an issue at github.com/Tesria/Tesria/issues: that is how it leaves beta.
Before you start
Administrator access to your provider, or someone who has it, to register Tesria there.
The address people open Tesria at, because the provider sends people back to it after they sign in.
Access to the server, to add the settings to
.env.
On this page, your-server stands for your server’s address: whatever you type into the browser to open Tesria, without https://. For example, if you open Tesria at https://wiki-server.local, then https://your-server/api/health means https://wiki-server.local/api/health.
Step 1: Register Tesria with your provider
In your provider’s admin console, add a new application (some call it a client). Choose the web or confidential type, and give it this redirect address:
https://your-server/signin-oidcThe provider then gives you three things to copy: its own address (called the authority or issuer), a client ID and a client secret.
Step 2: Add them to .env
OIDC_AUTHORITY=https://idp.example.com/realms/company
OIDC_CLIENT_ID=tesria
OIDC_CLIENT_SECRET=the-secret-from-the-provider
OIDC_DISPLAY_NAME=Company SSOOIDC_DISPLAY_NAME is what the sign-in button says, here Sign In With Company SSO. Without it, the button says Sign In With Single sign-on.
Step 3: Restart Tesria
docker compose up -d appStep 4: Try it
Sign out (Sign Out is at the top right of your profile page) and open the sign-in page: it now has the Sign In With button. Choose it, sign in at your provider, and you come back to Tesria signed in. If something is wrong, you land back on the sign-in page with the reason.
Which account someone gets
Someone who has signed in with SSO before gets the same account every time, even if their email address changes at the provider. An account with no Tesria password takes the new address when they next sign in, as long as the provider says it has confirmed it and no other account has it.
Someone who already has a Tesria account with the same email address is connected to it, but only if the provider says it has confirmed that address. Otherwise anyone who could claim the address at the provider could take over the account.
Someone new gets a new account with no Tesria password, as long as Allow Public Registration is on (Admin, Settings, Access). When it is off, they are turned away: send them an invite, let them create their account from it, and from then on SSO signs them in to that account. See Invites.
Two-factor sign-in
For most people who use SSO it is the provider’s job. An account made by SSO has no Tesria password, and its profile says the provider handles two-factor.
An account with Tesria two-factor on is asked for its code after SSO too. Someone who had a Tesria account with two-factor, and was then connected to SSO, comes back from the provider to Tesria’s One More Step page and signs in only with a code from their authenticator app or a recovery code, exactly as after a password. SSO is another way in, not a way around the second step.
Require Two-Factor for Administrators (Admin, Security (Admin is in the top bar; in a narrower window or on a phone it is in the ☰ menu at the left of the top bar, and a tab that does not fit is under ••• at the end of the tabs)) applies to administrators who sign in with SSO as well. One with no Tesria password sets up Tesria’s own two-factor from the profile within a few minutes of signing in, and until then the administration pages stay closed to them, as for anyone else.
Testing with a provider on plain HTTP on the same machine? Add OIDC_REQUIRE_HTTPS_METADATA=false. Never leave it that way for a real provider.
Applies to | Tesria 0.5 and later |
|---|---|
Updated | September 30, 2026 |
Changes | Revised. |