Menu AuthGuardHelp centre
Portuguêsauthguard.pt

Developers · SAML

Integrate a SAML 2.0 service provider

  • 1 min read
  • SaaS · Self-hosted

AuthGuard is a SAML 2.0 identity provider. This article sums up what a service provider (SP) needs to integrate.

Identity provider details

ItemValue
Entity ID and metadatahttps://<host>/saml/<organization>/metadata
SSO (HTTP-Redirect and HTTP-POST)https://<host>/saml/<organization>/sso
Sign-outhttps://<host>/saml/<organization>/logout
CertificatePEM with a SHA-256 fingerprint, valid 730 days

<organization> is the organization's internal identifier (Tenant ID).

Request rules

  • The AssertionConsumerServiceURL (or its index) must exactly match a registered ACS (https). Protection lies in the exact registration: AuthnRequest signatures are not verified.
  • Responses always go by HTTP-POST; Artifact and Redirect are not supported.
  • ForceAuthn forces a new confirmation; IsPassive without a usable single sign-on session returns NoPassive.
  • RelayState is returned as received.

The response

  • RSA-SHA256 signature of the response, the assertion or both (configurable).
  • Assertion lifetime of 60 to 600 seconds (default 300).
  • NameID: email, pairwise random identifier (persistent), user UUID or directory user name.
  • Up to 32 attributes: email, user_id, groups, directory_username, role or constants.

Error statuses

StatusCause
RequestDeniedThe access policy refused (federation.authorize, resource saml: plus the application identifier)
NoPassivePassive request without a usable session
NoAuthnContextRequested authentication context not accepted
UnknownPrincipalThe NameID source has no value for this person

Not supported

SAML Single Logout, encrypted assertions and account creation at the SP (no outbound SCIM).

Error codes in this article

Article referencedev-saml-integrationquote it to support to identify this article. Checked against the product at commit 5f6607a8.