Sign in to SAML applications
Use Scrydon as your organization's SAML 2.0 identity provider for applications that only speak SAML, and as the federated identity provider of a Microsoft 365 domain in Microsoft Entra ID.
Many applications, government ones especially, accept only SAML 2.0, and Microsoft Entra ID federates a domain only over SAML or WS-Federation. For those, Scrydon is also a SAML identity provider: your members sign in to Scrydon, and Scrydon sends the application a signed assertion that says who they are.
Your organization has an identity provider of its own. It lives under your organization's issuer, with its own signing certificates. No other organization shares its entity or its keys. Turn your organization's issuer on first: until you do, the SAML endpoints answer 404.
Everything below is under Settings → Organization → Apps, on the SAML apps and SAML identity provider tabs.
Only an owner or an admin of the organization can register a SAML application or change one. Every change, and every assertion Scrydon issues or refuses, is recorded in the audit log.
Your identity provider's values
An application asks for these. Copy them from the SAML identity provider tab; never type them by hand.
| Value | Where |
|---|---|
| Entity id (issuer) | <your organization's issuer> |
| Metadata | <entity>/saml/metadata |
| Single sign-on | <entity>/saml/sso (HTTP-Redirect and HTTP-POST) |
| Single logout | <entity>/saml/slo (HTTP-Redirect) |
Most applications only need the metadata URL: it carries the entity id, both endpoints and the signing certificates.
Register an application
On the SAML apps tab, select Register SAML app. Register an application from its own SAML metadata, as a file you upload or a URL Scrydon fetches. Scrydon reads its entity id, its assertion consumer service (ACS) URLs, its logout URL and the certificate it signs requests with.
- Every ACS and logout URL must be
https://. - A metadata URL must be public. Scrydon does not fetch a private, loopback or link-local address.
- A metadata file is limited to 512 KiB, and one with a
DOCTYPEis refused.
Then choose:
- Who may sign in. All members of your organization, or only the teams and people you assign. This works the same way as for OIDC apps; see Who can use an app.
- Require signed requests. On by default: Scrydon refuses an authentication request the application has not signed with the certificate in its metadata. Turn it off only for an application that cannot sign.
- Allow IdP-initiated sign-in. Off by default. When it is on, a member can start sign-in from Scrydon, and the response answers no request.
What Scrydon sends
-
A signed assertion, RSA-SHA256 with a 3072-bit key. Scrydon never signs with SHA-1, and refuses a request signed with SHA-1.
-
A persistent NameID: a stable, opaque value for that member in that application. It is not the member's email, and two applications receive different values for the same member.
-
The audience and recipient of the one application and ACS URL that asked. Each request is used once: replaying it is refused.
-
An authentication context that says how the member signed in:
How the member signed in AuthnContextClassRefPassword urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransportCertificate as the only factor urn:oasis:names:tc:SAML:2.0:ac:classes:X509Two factors https://refeds.org/profile/mfaSmart card urn:oasis:names:tc:SAML:2.0:ac:classes:SmartcardPKIPasskey urn:scrydon:acr:phishing_resistant
When a request carries ForceAuthn="true" and the member signed in before
it, Scrydon asks them to sign in again.
Who is refused
Scrydon issues nothing, and records the refusal, when the member:
- is not a member of your organization;
- is not assigned to the application;
- is suspended;
- signed in below your organization's sign-in strength floor. Scrydon answers with a refusal; it does not ask them to sign in again more strongly.
Signing certificates
Your identity provider keeps two certificates: the current one, which signs, and the next one, which is already in the metadata. An application that refreshes your metadata trusts the next certificate before it signs anything, so rotation causes no interruption.
- Rotate certificate makes the next certificate current and creates a new next one. The old certificate leaves the metadata.
- Retire removes a certificate at once. Applications that still trust only that certificate stop accepting sign-ins until they load your new metadata.
Each certificate is valid for one year. Private keys never leave Scrydon.
An application that stores a certificate instead of reading your metadata, Microsoft Entra ID included, must be given the new certificate before you rotate. Entra accepts a next signing certificate for exactly this.
Federate a Microsoft 365 domain with Entra ID
Your members can then sign in to Microsoft 365 with Scrydon. Register the application with the Microsoft Entra ID profile and list the domains to federate under Federated domains. Each domain must be:
- a verified domain of your organization;
- a domain whose members sign in with Scrydon itself. A domain whose members sign in through another identity provider would send them in a loop between Scrydon and Entra, so Scrydon refuses it.
With this profile:
- the NameID is the member's Entra
ImmutableID; - the
IDPEmailattribute carries their user principal name, the address Microsoft 365 knows them by. A member whose user principal name is not at a federated domain is refused, rather than signed in as someone else or no one; - every sign-in with two factors, a smart card or a passkey is sent as
http://schemas.microsoft.com/claims/multipleauthn.
The application's Microsoft Entra tab shows what to set on the domain in Entra
(internalDomainFederation in Microsoft Graph):
| Entra setting | Value |
|---|---|
issuerUri | your entity id |
passiveSignInUri | your single sign-on URL |
signOutUri | your single logout URL |
metadataExchangeUri | your metadata URL |
signingCertificate | the current certificate |
nextSigningCertificate | the next certificate |
preferredAuthenticationProtocol | saml |
federatedIdpMfaBehavior | enforceMfaByFederatedIdp |
isSignedAuthenticationRequestRequired | true |
promptLoginBehavior | nativeSupport |
Converting a domain to federated changes how everyone at that domain signs in to Microsoft 365, and Microsoft warns it can take up to two hours to take effect. Try it on a test domain first, keep a cloud-only Global Administrator whose account is not at the domain, and plan the change with your Scrydon contact. Scrydon asks you to confirm that account exists before it switches the domain.
Before you federate
On the Microsoft Entra tab, above Set up in Entra, a list headed Before you federate shows what must be in place before you switch a domain. It has a count such as "3 of 8 ready" and a Check again control. Scrydon only reads: the list changes nothing in Scrydon or in Entra.
Each row shows Ready, To do, Needs attention or Not checked. Not checked means Scrydon could not read that fact yet. A row that is not ready links to the screen that fixes it. When all eight rows are ready, the heading reads Ready to federate.
Six rows are read from your organization's settings:
| Requirement | What it means | Where to fix it |
|---|---|---|
| The organization issuer is on | Without it Scrydon has nothing to sign with. | Settings → Platform → Identity → Issuer |
| The domain is a verified domain of the organization | Only a verified domain can be federated. | Settings → Platform → Identity → Domains |
| Minimum authentication strength is Two factors or stronger | Microsoft is told to trust Scrydon for the second factor, so Scrydon has to ask for one. See sign-in strength. | Settings → Governance → Identity, Authentication requirements |
| The application requires signed requests | Scrydon tells Entra to sign its requests. With Require signed requests on, an unsigned one is refused. | The application's Settings tab |
| People have access to the application | A person without access is refused when Microsoft sends them to Scrydon. | The application's Access tab |
| The signing certificates are valid for more than 30 days | A certificate that ends sooner needs attention. Rotate it before you switch. | Settings → Organization → Apps → SAML identity provider |
Two rows are read from Microsoft Entra, through a Microsoft connection:
| Requirement | What it means | Where to fix it |
|---|---|---|
| A Microsoft connection has the Entra domain federation permission | The permission is Domain-InternalFederation.ReadWrite.All, consented by a Global Administrator. Scrydon cannot list a connection's permissions, so the row turns ready when it can read the domain through the connection. | The Microsoft extension, under Settings → Platform → Extensions |
| The domain is a domain of the Entra tenant and still signs in with Microsoft Entra | Scrydon reads how the domain signs in. A domain that signs in through another identity provider needs attention. | In Microsoft Entra |
If the domain signs in through another identity provider, switch it back to Entra in Microsoft first. Scrydon never takes over a domain federated elsewhere. If Microsoft refuses the read, the row shows Microsoft's answer. The usual causes are a connection without the permission and a domain that is not in that tenant. The row cannot tell which, so it names both.
Two things Scrydon cannot see are listed under Only you can confirm. The confirmation dialog asks you to tick both before it sends the switch:
- A cloud-only Global Administrator exists outside the domain. It is your way
back in if sign-in through Scrydon fails, for example an account at your
tenant's
onmicrosoft.comdomain. - The people you gave access exist in Entra with a matching
ImmutableID. Scrydon sends it as the NameID, and a person without a match cannot sign in. With Provisioning on, Scrydon creates the accounts with it.
Sign in through Scrydon is visible from the start. It stays disabled until all eight rows are ready, and next to it the tab says how many requirements are still open.
Once Entra reports that the domain signs in through Scrydon, the list becomes While federated, keep these true. It has six rows: the issuer, the verified domain, the authentication strength, signed requests, the signing certificates, and that Entra holds this organization's current certificates. When Entra holds older certificates than the organization signs with, that row needs attention and carries an Update certificates action. The box below offers Switch back to Entra.
The list is guidance in this screen. It does not check or block the values you enter in Microsoft Entra by hand.
Set up in Entra
Instead of entering the Entra values by hand, you can let Scrydon set them. This is optional, and Scrydon changes nothing in your tenant until you ask it to.
- Connect the Microsoft extension and grant its Entra domain
federation permission (
Domain-InternalFederation.ReadWrite.All). A Global Administrator must consent to it. It is separate from the extension's other permissions, so you can grant it for the change and remove it afterwards. - On the application's Microsoft Entra tab, under Set up in Entra, choose the connection and a federated domain. The tab reads the domain's sign-in from Microsoft as soon as both are chosen. With a single connection that is when the tab opens, for the application's first domain. Check sign-in and Check again read it again.
- Scrydon shows how the domain signs in now and offers the change that fits:
- signs in with Microsoft Entra: Sign in through Scrydon. The button stays disabled until all eight rows of the list above are ready;
- signs in through Scrydon: Switch back to Entra, and Update certificates when Entra holds older certificates than Scrydon signs with (do this before and after you rotate a certificate);
- signs in through another identity provider: nothing, and its row needs attention. Scrydon never takes over a domain federated elsewhere; switch it back to Entra in Microsoft first.
- Confirm. To sign in through Scrydon, the dialog asks you to tick the two items under Only you can confirm first. Microsoft can take up to two hours to apply the change; check the sign-in again later.
Scrydon sends only your organization's own values and certificates, and
records each request in your audit log
(saml_idp.entra_domain.federation_requested,
saml_idp.entra_domain.switch_back_requested) before it calls Microsoft. Only
an organization owner or admin can make the change, and only from this screen:
scripts, notebooks and agents can read a domain's federation through the
Microsoft extension, but cannot change it.
What this does not cover:
- Only modern-authentication clients sign in. Older Office clients and protocols that need WS-Trust or ECP do not.
- Scrydon does not encrypt assertions.
- Signing out of one application does not sign the member out of the others.