Skip to content

SAML 2.0

Configuration lives under Admin → Single sign-on → Providers → SAML 2.0. Choose your provider there: while SAML is not configured, the page shows these steps with your values and Copy buttons.

Each value contains your organisation’s short name (acme-rockets below).

Value Example Also called
SP entity ID (audience) https://portal.seylo.in/api/auth/saml/acme-rockets/metadata Entity ID, Audience URI, Identifier, Application SAML audience
ACS URL (reply URL) https://portal.seylo.in/api/auth/saml/acme-rockets/acs Assertion consumer service URL, Reply URL, Single sign-on URL
Sign-on URL (start URL) https://portal.seylo.in/api/auth/saml/acme-rockets/login Start URL, Application start URL — optional
  • Sign both the response and the assertion, with SHA-256 or stronger. Seylo refuses an unsigned response, an unsigned assertion and SHA-1.
  • Send the person’s email address (as the NameID or an attribute), and an attribute listing their groups or roles.
  • Start sign-ins from Seylo. Seylo refuses responses it did not ask for (IdP-initiated); an app tile must open the Sign-on URL.
  • There is no single-logout URL to configure; Seylo does not use one.
  1. Add a custom SAML application.

    IAM Identity Center console → Applications → Customer managed tab → Add application → Setup preference: I have an application I want to set up → Application type: SAML 2.0 → Next.

    • Display name: Seylo.
    • Under IAM Identity Center metadata, copy the IAM Identity Center SAML metadata file URL — it goes into Seylo.
    • Application start URL: the Sign-on URL.
    • Application metadata: Manually type your metadata values — Application ACS URL = the ACS URL, Application SAML audience = the SP entity ID. Submit.
  2. Map attributes. The application → Actions → Edit attribute mapping:

    Attribute Value Format
    Subject ${user:subject} persistent
    email (Add new attribute mapping) ${user:email} basic

    Save changes. Groups: AWS does not document a groups attribute for custom applications. Many setups add groups = ${user:groups}, which sends group IDs, not names. If the test shows no groups attribute, grant roles with a Base role and Seylo’s Users tab instead.

  3. Assign people on the application’s Assigned users and groups tab.

Seylo field Value
Identity provider metadata URL The IAM Identity Center SAML metadata file URL from step 1 (or paste the downloaded file into the XML box).
Role attribute groups (filled in already). Map each group ID to a Seylo role; Identity Center → Groups shows each group’s ID.
Email attribute email.
  1. Add a relying party trust. AD FS Management → Relying Party Trusts → Add Relying Party Trust → Claims aware → Start → Enter data about the relying party manually. Display name Seylo; skip the encryption certificate. Configure URL: tick Enable support for the SAML 2.0 WebSSO protocol, paste the ACS URL. Configure Identifiers: add the SP entity ID. Choose an access control policy (for example, a group), Finish.

  2. Issue email and groups. Right-click the trust → Edit Claim Issuance Policy → Add Rule:

    • Send LDAP Attributes as Claims: attribute store Active Directory; E-Mail-Addresses → E-Mail Address; Token-Groups - Unqualified Names → Role (security groups only).
    • Transform an Incoming Claim: incoming E-Mail Address, outgoing Name ID, format Email.
  3. Sign with SHA-256, and sign the whole response. Trust Properties → Advanced → Secure hash algorithm: SHA-256. AD FS has no screen for signing the response as well as the assertion; on the AD FS server run:

    Terminal window
    Set-AdfsRelyingPartyTrust -TargetName "Seylo" -SamlResponseSignature MessageAndAssertion
Seylo field Value
Identity provider metadata URL https://<your AD FS host>/FederationMetadata/2007-06/FederationMetadata.xml
Role attribute http://schemas.microsoft.com/ws/2008/06/identity/claims/role (filled in already) — not roles. Map group names to Seylo roles.

Create a custom SAML 2.0 application, paste the three values above, sign the response and the assertion with SHA-256, choose NameID format email address or persistent, and add an email attribute and a groups attribute. Then:

Seylo field Value
Identity provider metadata URL The provider’s IdP metadata URL (or paste the XML).
Role attribute The groups/roles attribute name.
Email attribute The email attribute name, if the NameID is not the email address.

Press Read metadata, confirm the certificate fingerprint with whoever runs the identity provider (metadata is not signed; the fingerprint is how you know it is theirs), map the role values on Attribute mapping, and Save SAML configuration. Seylo’s own SP metadata is then downloadable from the same card, if your provider prefers importing a file.

XML signature validation uses @node-saml/node-saml rather than hand-rolled XML handling. Verification processes the bytes the signature actually covered, which defeats signature-wrapping attacks, and validates only against the certificate you configured — never one embedded in the received document.

What you see What it means and what to do
signature-invalid The response or the assertion is unsigned, or signed with a certificate you did not import. Sign both (AD FS: the PowerShell line above); re-import metadata after a certificate rollover.
weak-signature-algorithm SHA-1. Switch the provider to SHA-256.
destination-mismatch The provider’s ACS / reply URL is not exactly Seylo’s ACS URL.
audience-mismatch The provider’s entity ID / audience is not exactly Seylo’s SP entity ID.
no-in-response-to The sign-in started at the provider (an app tile). Point the tile at the Sign-on URL.
assertion-expired The clocks disagree. Fix NTP; the accepted difference is on Attribute mapping, at most 300000 ms.
saml-not-configured (404) Wrong organisation name in the ACS URL, a suspended organisation, or no SAML configuration. One error for all three on purpose.

Checked on 2026-10-15: AWS: set up your own SAML 2.0 application · AWS: attribute mappings · AD FS: Set-AdfsRelyingPartyTrust · AD FS: SHA-256 guidance · AD FS as a SAML provider