Skip to content

Microsoft Entra ID

This page is for the Entra administrator who sets up sign-in to Seylo. You do not need to have used Seylo before. Allow about ten minutes.

  • A Microsoft Entra account that can create app registrations (Application Administrator or Cloud Application Administrator).
  • A Seylo account with the admin role.
  • No client secret is needed for sign-in. Seylo signs in from the browser, as a single-page application.
Value Example Where it goes in Entra
Sign-in redirect URI https://portal.seylo.in Authentication → Add Redirect URI → Single-page application
Test sign-in redirect URI (optional) https://portal.seylo.in/api/auth/sso/test/callback Authentication → Add Redirect URI → Web — only for the Test tab

The sign-in redirect URI is the portal’s address with no trailing slash and no path. If your organisation runs its own Seylo installation, use its address; the Seylo page always shows the exact value.

  1. Register the application.

    Microsoft Entra admin center (entra.microsoft.com) → Entra ID → App registrations → New registration.

    • Name: something people recognise, for example Seylo.
    • Supported account types: the single-tenant option, Single tenant only (older screens call it Accounts in this organizational directory only).
    • Select Register.
  2. Add the redirect URI.

    In the new app registration: Manage → Authentication → Add Redirect URI, choose Single-page application, paste the sign-in redirect URI and select Configure.

    It must be Single-page application, not Web. Seylo completes the sign-in in the browser, and Entra only allows that for the single-page type.

  3. Let Seylo request a token for itself.

    • Expose an API → next to Application ID URI select Add, keep the suggested api://<client id>, Save.
    • Add a scope: Scope name access_as_user, Who can consent Admins and users, any display names and descriptions, State Enabled, then Add scope.
    • Manifest: set requestedAccessTokenVersion to 2 (inside api) and Save. If it is left empty, Entra issues older tokens from https://sts.windows.net/<tenant id>/, which Seylo refuses as an unknown issuer.
  4. Create app roles.

    App roles → Create app role, once per Seylo role you will use:

    Field Value
    Display name Viewer
    Allowed member types Users/Groups
    Value viewer
    Description anything
    Do you want to enable this app role? ticked

    Select Apply, and repeat with the values releaser, approver and admin. Any values work - you map them in Seylo - but matching Seylo’s role names keeps the mapping obvious.

  5. Give the roles to people.

    Entra ID → Enterprise apps → All applications → the app with the same name → Users and groups → Add user/group. Pick the people or groups, Select a role, Assign. Assigning a group requires Microsoft Entra ID P1 or P2.

    Recommended: in the enterprise app’s Properties, make assignment required, so only people you assigned can sign in at all.

Everything is on the app registration’s Overview page.

Seylo field Where it is in Entra
Directory (tenant) ID Overview → Directory (tenant) ID — a GUID. A verified domain such as acme.example also works.
Application (client) ID Overview → Application (client) ID — a GUID. Not the Object ID.
Client secret (optional) Only for Sign in for real on the Test tab. Certificates & secrets → Client secrets → New client secret, then copy the Value — not the Secret ID — before leaving the page; Entra never shows it again.

Then press Check the provider. Seylo reads Entra’s published configuration and shows the issuer and signing keys it found; confirm they mention your directory ID and select Save provider.

You do not type the discovery URL, the audiences or the API scope: Seylo works them out from the IDs above (api://<client id>/access_as_user, and the client ID plus api://<client id> as audiences). The Advanced section is there only if your setup differs.

Leave “Require this directory” empty unless your app registration is multi-tenant and shared with another Seylo organisation.

  • Role claim: roles (filled in already).

  • Role map: one line per app-role value, value from Entra = Seylo role:

    viewer = viewer
    releaser = releaser
    approver = approver
    admin = admin
  • Base role (optional): a role everyone who signs in gets, e.g. viewer.

Token configuration → Add groups claim puts a groups claim in the token. Entra sends group object IDs (GUIDs) by default, not names - names are only available for groups synchronised from on-premises Active Directory. Set the role claim to groups and map the object IDs; the test report prints them exactly as they arrive.

Open Test in Seylo’s Single sign-on page.

  • Sign in for real needs the test redirect URI registered as a Web redirect URI and a client secret saved, because the test exchanges the code on Seylo’s server.
  • Without a secret, sign in to Seylo in another browser with an assigned account: that is the real sign-in path.
What you see What it means and what to do
AADSTS50011 The reply address does not match. Register exactly the sign-in redirect URI, under Single-page application.
cross-origin token redemption is permitted only for the 'Single-Page Application' client-type The redirect URI is registered as Web. Remove it there and add it under Single-page application.
AADSTS50105 The person is not assigned to the app and assignment is required. Assign them in Enterprise apps → Users and groups.
AADSTS65001 Consent is missing for the access_as_user scope. Check Who can consent is Admins and users, or grant admin consent.
No tenant is registered for token issuer "https://sts.windows.net/..." Entra issued an old-format token. Set requestedAccessTokenVersion to 2 in the Manifest (step 3).
Token validation failed: unexpected "aud" claim value The token was issued to a different client. Check the Application (client) ID you entered.
FINAL: none - every action will be refused Sign-in worked but no role mapped: the person has no app role assigned, or the role map lacks their value.

More in troubleshooting.

Checked on 2026-10-15: Register an application · Add a redirect URI · Expose a web API · App roles · Assign users and groups · Access tokens · Client secrets · Error codes · Optional and group claims