# OneLogin SAML single sign-on

<!-- Generated by scripts/generate.ts. Do not edit. -->

Add a SAML app in OneLogin, paste the values from this setup, give your users access and share the app's metadata with us.

:::caution[Verification]
Not yet verified on a real OneLogin tenant. It was written from the public OneLogin documentation, so labels in the admin console may differ slightly.
:::

The values in braces, such as `{sp_entity_id}`, are specific to your connection. The setup link from the application you are connecting shows them with a copy button. The same steps appear there.

## Steps

<ol class="idp-steps">

<li class="idp-step">

<a id="create-app"></a>

### Add a SAML app

In the OneLogin admin portal, go to Applications > Add App, search for the custom SAML connector, select it, enter a display name and select Save.

:::caution[Labels not confirmed in step 1]
No OneLogin page readable on 2026-10-11 names the custom SAML connector; the step is written generically.
:::

</li>

<li class="idp-step">

<a id="audience"></a>

### Enter the audience

On the app's Configuration tab, paste `{sp_entity_id}` into the audience (entity ID) field.

<div class="setup-values">

Paste into OneLogin:

- SP entity ID: `{sp_entity_id}`

</div>

Fixes: [`saml_audience_mismatch`](/errors/saml_audience_mismatch/)

:::caution[Labels not confirmed in step 2]
Field label not confirmed from a OneLogin source on 2026-10-11.
:::

</li>

<li class="idp-step">

<a id="acs"></a>

### Enter the ACS URL

Paste `{acs_url}` into the recipient field and the ACS (consumer) URL field. If there is an ACS URL validator field, paste the same URL there too. Select Save.

<div class="setup-values">

Paste into OneLogin:

- ACS URL: `{acs_url}`

</div>

Fixes: [`saml_destination_mismatch`](/errors/saml_destination_mismatch/), [`saml_response_malformed`](/errors/saml_response_malformed/)

:::caution[Labels not confirmed in step 3]
Field labels not confirmed from a OneLogin source on 2026-10-11.
:::

</li>

<li class="idp-step">

<a id="name-id"></a>

### Send the email address as the name ID

On the SSO or Parameters tab, make sure the name ID is the user's email address.

Fixes: [`saml_nameid_missing`](/errors/saml_nameid_missing/)

</li>

<li class="idp-step">

<a id="signing"></a>

### Check the signing settings

On the SSO tab, sign the assertion (or both the assertion and the response) and use SHA-256.

Fixes: [`saml_signature_missing`](/errors/saml_signature_missing/), [`saml_signature_algorithm_weak`](/errors/saml_signature_algorithm_weak/)

:::caution[Labels not confirmed in step 5]
Field labels not confirmed from a OneLogin source on 2026-10-11.
:::

</li>

<li class="idp-step">

<a id="attributes"></a>

### Add the attributes

On the Parameters tab, add email, firstName and lastName parameters mapped to the user's email, first name and last name, and select Include in SAML assertion for each.

Fixes: [`saml_email_missing`](/errors/saml_email_missing/)

</li>

<li class="idp-step">

<a id="assign"></a>

### Give people access

Assign the app to the users or roles who should sign in with single sign-on.

Fixes: [`saml_idp_status_error`](/errors/saml_idp_status_error/)

:::caution[Labels not confirmed in step 7]
Assignment labels not confirmed from a OneLogin source on 2026-10-11.
:::

</li>

<li class="idp-step">

<a id="metadata"></a>

### Share the identity provider metadata

Download the app's SAML metadata (or the issuer URL and X.509 certificate) and add it to this setup. Do this again whenever the certificate changes.

Fixes: [`saml_signature_invalid`](/errors/saml_signature_invalid/), [`saml_issuer_mismatch`](/errors/saml_issuer_mismatch/)

:::caution[Labels not confirmed in step 8]
Metadata download location not confirmed from a OneLogin source on 2026-10-11.
:::

</li>

<li class="idp-step">

<a id="test"></a>

### Test the connection

Run a test sign-in in this setup, signing in as a user who has access to the app.

</li>

</ol>

<a id="standby"></a>

## Optional: add the standby ACS URL

If our main network ever has an outage, sign-ins can continue through a standby address, but only if OneLogin accepts it. If the app lets you add more than one ACS URL, add `{standby_acs_url}` as the second one and keep `{acs_url}` as the default. If it allows only one, skip this step. Then confirm in this setup that you added it.

<div class="setup-values">

Paste into OneLogin:

- Standby ACS URL: `{standby_acs_url}`
- ACS URL: `{acs_url}`

</div>

This step is optional. See [standby route behavior](/trust/standby/) for what the standby address does during an outage.

## Sources

- [Dev Overview of SAML (OneLogin Developers)](https://developers.onelogin.com/saml), read on 2026-10-11
- [Create a SCIM test app (OneLogin Developers)](https://developers.onelogin.com/scim/create-app), read on 2026-10-11
