Connect SecureAuth SAIdP
SecureAuth SAIdP has two presets on the Create Connection page: one for SAML, one for OpenID Connect (OIDC). A preset is not a new connection type: it opens the ordinary SAML or OIDC connection form with the fields SecureAuth SAIdP needs already filled in. You still provide your tenant's own values, and everything the preset sets stays editable afterward on the connection's Configuration, Attributes and Mappings tabs.
Before you begin
Have the following ready, depending on which preset you use:
- SAML – your SecureAuth SAIdP metadata URL, or the metadata XML itself.
- OIDC – your SecureAuth SAIdP issuer URL and client ID.
Connect SecureAuth SAIdP to SecureAuth Connect
-
In your workspace, go to Authentication > Providers, then click Create Connection. The same two tiles also appear under External Providers in the simplified identity providers list.
-
Click the SecureAuth filter chip to narrow the list to SecureAuth-native templates. The SecureAuth SAIdP tiles are pinned at the front of the grid.
-
Select SecureAuth SAIdP (SAML) or SecureAuth SAIdP (OpenID Connect), then click Next.
-
Complete the remaining fields:
- SAML – Enter a Metadata URL, or switch Metadata delivery mode to File or RAW XML and provide the IDP Metadata. The Name field is pre-filled with "SecureAuth SAIdP SAML"; the Entity ID and ACS URL are generated for you to register at your SecureAuth SAIdP tenant.
- OIDC – Enter the Issuer URL and Client ID. The Name field is pre-filled with "SecureAuth SAIdP"; no client secret is needed because the preset sets Authentication Method to None (PKCE).
-
Save your changes.
The connection appears on the Providers list using the name from the preset. Rename it, or change any other field, at any time on the connection's tabs.
What the preset configures
SAML
Name ID Format on the Configuration tab reads urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified, the default every new SAML connection gets (not something unique to this preset). The Attributes tab adds:
| Variable name | Display name |
|---|---|
saml_attributes.mail | |
saml_attributes.firstname | First Name |
saml_attributes.lastname | Last Name |
saml_name_id | nameID |
saml_attributes.name | name |
The Mappings tab maps those attributes to the SecureAuth authentication context:
| Source | Target |
|---|---|
saml_attributes.mail | email |
saml_attributes.firstname | given_name |
saml_attributes.lastname | family_name |
saml_attributes.name | name |
Static true | email_verified |
OIDC
The Attributes tab has the standard OIDC claim set (the access token's aud, iss, iat, exp and scp, and the ID token's aud, iss, iat, exp, email, name and preferred_username), plus given_name and family_name from the ID token. The Mappings tab maps:
| Source | Target |
|---|---|
Access token scp | scp |
ID token name | name |
ID token email | email |
ID token preferred_username | preferred_username |
ID token family_name | family_name |
ID token given_name | given_name |
Static true | email_verified |
To customize either list, click + Add attribute on the Attributes tab, or + Add mapping / + Add static mapping on the Mappings tab, then Save mappings.
Test the connection
-
Confirm the provider is enabled on the Providers list.
-
Open an application that uses SecureAuth Connect for sign-in, or the built-in User Portal.
-
Start a sign-in and select the provider by the name you gave it.
-
Authenticate with a SecureAuth SAIdP account. SecureAuth issues its tokens with the user data mapped from SecureAuth SAIdP.