SSO & cloud providers

SSO with Microsoft Entra ID

Register an Entra ID app for Eddytor sign-in and connect it to your organisation.

Register a single-tenant app in Microsoft Entra ID, then connect it as your organisation's OIDC connection. This app is for sign-in only - storage access uses a separate provider app.

Register the app

In the Entra admin center:

  1. App registrations → New registration. Name it Eddytor SSO. Supported account types: Accounts in this organizational directory only.
  2. Redirect URI: platform Web, ${server.public_url}/v1/oauth/sso/callback.
  3. Copy the Application (client) ID and the Directory (tenant) ID.
  4. Certificates & secrets → New client secret → copy the value.
  5. API permissions → Microsoft Graph, delegated: openid, email, profile → Grant admin consent.
  6. Token configuration → Add optional claim → token type ID → email.
  7. Recommended: Enterprise applications → Eddytor SSO → Properties → Assignment required = Yes, then assign the users or groups who may use Eddytor. Anyone who can sign in to the app with an address at your domain is created in your organisation on first sign-in.

Connect it

eddytor create sso \
  --issuer-url "https://login.microsoftonline.com/<tenant-id>/v2.0" \
  --client-id "<application-client-id>" \
  --client-secret "<client-secret>" \
  --email-domain example.com \
  --default-role editor

The REST body and field rules are on SSO with OIDC.

Accounts without an email address

Admin accounts often have no email address, so Entra sends no email claim. Let them sign in with their user principal name (UPN, the preferred_username claim) instead:

eddytor set sso --email-claim-fallback preferred_username

Over REST, PATCH the connection with {"emailClaimFallback": "preferred_username"}. The UPN must be at the connection's email domain. Guest accounts (#EXT# UPNs) are refused. Eddytor refuses the setting unless the issuer is https://login.microsoftonline.com/<tenant-id>/v2.0.

Heads up

Eddytor identifies users by address. If an account that signed in with its UPN later gets a different email address in Entra, its next sign-in creates a new Eddytor user.

Verify

Sign out, run eddytor login, and enter an address at your domain. The browser goes to the Microsoft sign-in page, then back to Eddytor, signed in.

Gotchas

  • Use the tenant ID in the issuer. /common, /organizations, and the domain form (…/contoso.com/v2.0) fail Eddytor's discovery check.
  • Accounts without an email address can't sign in until you set the email-claim fallback. The browser shows SSO authentication failed.
  • The client secret expires. Store the new one with eddytor set sso --client-secret <value> before the old one runs out.

On this page