Skip to content

Okta

This page is for the Okta administrator who sets up sign-in to Seylo. You do not need to have used Seylo before. Seylo signs in from the browser, so the Okta app is a Single-Page Application and has no client secret.

Value Example Where it goes in Okta
Sign-in redirect URI https://portal.seylo.in/ Sign-in redirect URIs — note the trailing /
Origin https://portal.seylo.in Security → API → Trusted Origins, type CORS
Test sign-in redirect URI (optional) https://portal.seylo.in/api/auth/sso/test/callback Sign-in redirect URIs, second line — only for the Test tab
  1. Create the app integration.

    Okta Admin Console → Applications → Applications (newer consoles: Applications and Resources → Applications) → Create App Integration.

    • Sign-in method: OIDC - OpenID Connect.
    • Application type: Single-Page Application. Next.
    • App integration name: Seylo. Grant type: keep Authorization Code.
    • Sign-in redirect URIs: the sign-in redirect URI (and the test one).
    • Sign-out redirect URIs: remove the default; Seylo does not use one.
    • Assignments → Controlled access: who may sign in. Limit access to selected groups is the usual choice. Save.
  2. Allow Seylo’s origin.

    Security → API → Trusted Origins → Add Origin: paste the origin, tick CORS (and Redirect), Save. Seylo finishes the sign-in with a call from the browser to Okta.

  3. Send group membership — Okta sends none by default.

    The app’s Sign On tab → OpenID Connect ID Token → Edit:

    Field Value
    Group claim type Filter
    Group claims filter name groups, Matches regex .*

    Save. Skipping this is the most common Okta problem: sign-in succeeds and nobody has any permissions. Once you know which groups you map, tighten the filter, e.g. Starts with Seylo-.

Seylo field Where it is in Okta
Okta domain Your Okta org’s address without https://, e.g. acme.okta.com.
Client ID The app’s General tab → Client Credentials → Client ID.
Client secret Leave empty — a Single-Page Application has none.

Press Check the provider, then Save provider.

From a plain domain Seylo uses Okta’s org authorization server (issuer https://acme.okta.com). It needs no extra Okta licence, and the groups claim from step 3 is configured on it.

If you already run a custom authorization server (issuer https://acme.okta.com/oauth2/default or /oauth2/<id>; it needs Okta’s API Access Management), enter that issuer in Okta domain instead. Then the groups claim belongs on that server (Security → API → Authorization Servers → the server → Claims → Add Claim, include in ID Token, value type Groups), and the server needs a scope named groups — the default server does not have one until you add it under Scopes.

  • Role claim: groups (filled in already).

  • Role map: one line per group, Okta group name = Seylo role:

    Seylo-Viewers = viewer
    Seylo-Approvers = approver
    Seylo-Admins = admin

Open Test in Seylo’s Single sign-on page and use Sign in for real — no secret is needed for Okta — or sign in to Seylo in another browser with an assigned account.

What you see What it means and what to do
The 'redirect_uri' parameter must be a Login redirect URI in the client app settings Add exactly the sign-in redirect URI, including the trailing /, to Sign-in redirect URIs.
The browser could not call the provider's token endpoint The origin is not a Trusted Origin with CORS ticked (step 2).
User is not assigned to the client application Assign the person, or a group they are in, on the app’s Assignments tab.
One or more scopes are not configured for the authorization server resource You entered a custom authorization server without a groups scope. Use the plain domain, or add the scope.
No tenant is registered for token issuer "..." The issuer differs from the one saved — usually org vs custom authorization server. Compare iss in the test report with the issuer shown after Check the provider.
FINAL: none - every action will be refused The groups claim is missing, or no group name is mapped. Check step 3, then add the names the report shows to the Role map.

Checked on 2026-10-15: Create OIDC app integrations · Create an Okta app for a SPA · Customize tokens with a groups claim · Authorization servers