Single sign-on (OIDC)
Connect your OpenID Connect identity provider so your team signs in to Screeb with SSO.
Screeb supports OpenID Connect (OIDC) Single Sign-On (SSO). Your team signs in to Screeb through your company’s Identity Provider (IdP), such as Okta, Microsoft Entra ID (Azure AD), Ping Identity, OneLogin, Auth0, JumpCloud or Keycloak, instead of using a separate Screeb password.
This page explains the setup and who owns each step.
Who is involved
Section titled “Who is involved”Setting up OIDC SSO takes a short back-and-forth between two people:
- Someone on your side with admin access to your Identity Provider, who can create and configure an application there.
- Someone on the Screeb side (your Customer Success contact, or support@screeb.app), who creates the matching connection in Screeb.
No code or integration work is needed on your end. Everything happens in your IdP’s admin console.
Overview of the process
Section titled “Overview of the process”OIDC needs fewer exchanges than SAML: the only value Screeb gives you, the redirect URI, is known in advance.
| Step | Who | What happens |
|---|---|---|
| 1 | You | Create an OIDC application for Screeb in your IdP, using Screeb’s redirect URI, and assign your users. |
| 2 | You | Send Screeb the issuer URL, client ID, client secret and the email domains your team signs in with. |
| 3 | Screeb | Creates your SSO connection, confirms your email domains and enables SSO for your organization. |
| 4 | Both | Test a real sign-in together before rolling it out. |
| 5 | Optional | Make SSO mandatory for your domains. |
Step 1: Create the OIDC application
Section titled “Step 1: Create the OIDC application”In your IdP’s admin console, create a new OIDC application for Screeb with these settings:
| Setting | Value |
|---|---|
| Application type | Web application (confidential client, with a client secret) |
| Grant type | Authorization Code |
| Sign-in redirect URI (or “callback URL”, “reply URL”) | https://auth.screeb.app/idps/callback |
| Scopes | openid, profile, email |
| Sign-out redirect URI | Not needed |
If your organization is hosted on a dedicated Screeb platform, the redirect URI uses that platform’s own domain. Your Screeb contact will tell you which one.
PKCE is supported. Tell your Screeb contact if your IdP requires it.
Claims
Section titled “Claims”Screeb reads the user’s identity from the standard OIDC claims, as returned by your IdP’s userinfo endpoint (or by the ID token, on request):
| Claim | Required? | Purpose |
|---|---|---|
sub |
Required (always sent) | Identifies the user. It must never change for a given user: Screeb uses it to recognize the same person on every sign-in. |
email |
Required | Matches the sign-in to the Screeb user. Without it, sign-in fails. |
email_verified |
Optional | If your IdP sends it, it must be true. A user whose address is marked as unverified is refused. |
given_name |
Recommended | Fills in the user’s first name in Screeb when the account is created. |
family_name |
Recommended | Fills in the user’s last name in Screeb when the account is created. |
The email and profile scopes normally make your IdP return these claims. If no name is sent, sign-in still works and the name stays blank until the user sets it in Screeb.
Assign users
Section titled “Assign users”Assign the users or groups who should have access to Screeb to the application. Users who are not assigned are refused by your IdP.
Notes for common IdPs
Section titled “Notes for common IdPs”- Okta: create an OIDC - OpenID Connect app integration of type Web Application, with the Authorization Code grant. The issuer is your Okta domain (
https://<your-org>.okta.com), orhttps://<your-org>.okta.com/oauth2/defaultif you use the default custom authorization server. Okta sendsemail_verified: make sure your users’ email addresses are verified in Okta. - Microsoft Entra ID: in App registrations, register a new application with a Web redirect URI, then create a client secret under Certificates & secrets. In Token configuration, add the optional claims
email,given_nameandfamily_name. The issuer ishttps://login.microsoftonline.com/<tenant-id>/v2.0. Entra client secrets expire: note the expiry date (see the FAQ). - Keycloak: create a client with Client authentication on and the Standard flow enabled. The issuer is
https://<your-keycloak-host>/realms/<realm>. Keycloak sendsemail_verified: make sure your users’ email addresses are verified.
Step 2: Send the connection details to Screeb
Section titled “Step 2: Send the connection details to Screeb”Send your Screeb contact:
| Value | Example |
|---|---|
| Issuer URL | https://login.acme.com (Screeb reads its configuration from <issuer>/.well-known/openid-configuration) |
| Client ID | 0oa1b2c3d4e5f6g7h8i9 |
| Client secret | Send it through a secure channel (a password manager share or a one-time secret link), never in plain email. |
| Email domains | acme.com, acme.fr |
The issuer’s discovery document (/.well-known/openid-configuration) must be reachable from the internet.
Step 3: Screeb enables SSO for your organization
Section titled “Step 3: Screeb enables SSO for your organization”Screeb then:
- creates your SSO connection from these details;
- confirms the email domains that belong to your organization;
- enables your SSO connection for your organization.
Your connection is private to your organization. It never appears on the public login page, and it is never offered to users outside your organization.
Step 4: Test the login
Section titled “Step 4: Test the login”Before rolling SSO out to your whole team, we schedule a short call to test a real sign-in end to end and check that the email and names come through correctly.
Step 5 (optional): Make SSO mandatory
Section titled “Step 5 (optional): Make SSO mandatory”By default, SSO is added to the existing login methods: your users can still sign in with their password, Google or Microsoft.
On request, Screeb can make SSO the only way in for addresses on your confirmed domains. Password sign-in, password sign-up, Google, Microsoft and any other SSO connection are then refused for those addresses. Passwords are not deleted: if SSO-only is switched off later, they work again.
People whose email is on another domain (agencies, contractors) are not affected and keep their usual login method.
We recommend switching SSO-only on once your existing users have signed in with SSO at least once (see the one-time confirmation below). Users who signed in with a password can still complete that confirmation afterwards, but users who only ever used Google or Microsoft would first have to set a password through Forgot password, because those methods are refused once SSO is mandatory.
What your users will see
Section titled “What your users will see”Signing in. Users open the Screeb login page, enter their work email and click Continue. Screeb recognizes the domain and sends them straight to your IdP, so they never see a password field. After signing in with your IdP, they land back in Screeb, signed in.
First SSO sign-in for an existing Screeb user. If someone already has a Screeb account (with a password, Google or Microsoft), Screeb asks them, once, to confirm the account by signing in with their existing method. Their SSO identity is then connected to the account, and from then on SSO alone is enough. This protects accounts: a sign-in from an IdP is never enough, on its own, to take over an account that already exists. The confirmation must happen within 10 minutes, and is cancelled after 3 wrong passwords (the user then simply starts again from the SSO sign-in).
New users. Someone who has no Screeb account yet gets one automatically on their first SSO sign-in. To give them access to your workspaces, invite them from Screeb, or ask your Screeb contact about automatic join for your email domains.
Invited users. Invitations work as usual. When SSO applies, the invitation link sends the person through your IdP, with no password to create.
Starting from your IdP’s app portal. Sign-ins must start from Screeb. To keep a tile in your app portal, point it at your connection’s direct sign-in link, which your Screeb contact can give you. In Okta, this goes in the Initiate login URI field of the application.
Which claims are required?
sub and email. given_name and family_name are recommended. If email_verified is sent, it must be true. See the claims table in step 1.
Should we choose OIDC or SAML? Whichever your IAM team prefers: both give your users the same experience. OIDC is usually quicker, because there is no metadata to exchange and nothing to configure on your side after Screeb creates the connection.
Our client secret is about to expire. What should we do? Create a new secret in your IdP and send it to your Screeb contact before the old one expires, so we can update the connection without interrupting sign-ins. Only delete the old secret once we confirm the switch.
Can we keep password login alongside SSO? Yes, that is the default. SSO only becomes mandatory if you ask for it (step 5).
How do we enforce multi-factor authentication? Through your IdP: Screeb relies on it to authenticate your users, so your IdP’s MFA policy applies to every SSO sign-in.
What happens when someone leaves the company? Once they are disabled or unassigned in your IdP, they can no longer sign in to Screeb. A Screeb session that is already open can stay valid for up to 30 days, so to cut access immediately, also remove the person from your organization’s members in Screeb. Automatic provisioning (SCIM) is not supported.
Does signing out of Screeb sign the user out of our IdP? No. Signing out of Screeb ends the Screeb session only. Front-channel and back-channel logout are not supported.
A user sees an error after signing in with our IdP. What should we check?
| What the user sees | Most likely cause |
|---|---|
| “Sign-in failed. Please try again…” | Your IdP returned no email claim (check the email scope and the claims configuration), or the client secret is wrong or expired. |
| “Your identity provider has not verified this email address…” | Your IdP sent email_verified: false for this user. Verify the address in your IdP. |
| “Your identity provider sent an address that is not a valid email…” | The email claim holds something other than a single email address. |
| “Your organization signs in with single sign-on…” | SSO is mandatory for this address, and the user tried another method (password, Google, Microsoft). They should enter their work email and continue with SSO. |
| “This platform is invitation-only…” | The platform only accepts invited users, and this person has not been invited yet. |
| Your IdP shows a “redirect URI mismatch” error | The redirect URI in your IdP application doesn’t exactly match the one in step 1. |
| Your IdP itself refuses the sign-in | The user isn’t assigned to the Screeb application in your IdP. |
Who do we contact if something isn’t working? Your Customer Success contact, or support@screeb.app.