> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/identity-verification/ial2-verification/saml.md).

# SAML

***

## Triggering IAL2 Verification Using SAML

Users can upgrade their own status to IAL2 in AdminX by using the 1Kosmos web-based identity-proofing flow. Tenant and community administrators can trigger this flow using SAML.

### Prerequisites

Before starting, ensure you have integrated your Service Provider (SP) for SSO as a SAML application. See **SSO Integration in AdminX** for more information on configuring your Service Provider (SP) in AdminX.

### Configuring Your Service Provider (SP) in AdminX

1. Navigate to your AdminX control panel and log in as a community or tenant administrator.
2. Go to the **Applications** page and find your SAML application. Click the pencil icon under **Actions** to edit the SAML application settings.
3. Click **Next** to view the SAML settings for your application.
4. Under **Claims Mapping**, click **Add new**.
5. Select `ial` from the drop-down menu under **BLOCKID LEDGER ATTRIBUTES**.
6. Enter a format to use with the attribute and click **Create**.

Administrators can optionally map an identity attribute to use with this SAML claim, such as the user's first or last name as shown on their driver's license or passport.

7. Click **Add new** once more to add another claims mapping.
8. Find the **identity attribute** you wish to add, such as `dl.lastname`, and assign a format.
9. Click **Create** to save.
10. Click **Next** once you have finished mapping all your SAML claims.
11. Click **Save** to complete the IAL claims mapping for your SAML application.

### Requesting IAL2 Verification as a Service Provider

Once the SAML attributes have been mapped in AdminX, Service Providers can request IAL2 verification using `RequestedAuthnContext` as part of the SAML request. When the branded claim is received by the IdP (1Kosmos), it triggers an IAL2 journey to elevate the user's identity assurance level.

```xml
<samlp:RequestedAuthnContext Comparison="exact">
  <saml:AuthnContextClassRef>urn:oasis:names:tc:SAML:2.0:ac:classes:IAL2</saml:AuthnContextClassRef>
</samlp:RequestedAuthnContext>
```

From a user's standpoint, they are redirected to AdminX to perform their identity verification instead of a standard login.

### SAML Responses

Depending on the user's current IAL level after performing their identity verification, the server returns different responses. The table below shows the SAML responses returned after a user has attempted an identity verification. These responses can be viewed using a SAML tracer if desired.

| Requested AuthnContext | User's IAL Level After Identity Verification                    | SAML Response                                                                                                                                                                                                                                 |
| ---------------------- | --------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| IAL2                   | IAL1 (Failed Identity Verification or Insufficient Information) | `<saml:AuthnContext/>`                                                                                                                                                                                                                        |
| IAL2                   | IAL2                                                            | `<saml:AuthnContext><saml:AuthnContextClassRef>urn:oasis:names:tc:SAML:2.0:ac:classes:IAL2</saml:AuthnContextClassRef></saml:AuthnContext>`                                                                                                   |
| IAL2                   | IAL3                                                            | `<saml:AuthnContext><saml:AuthnContextClassRef>urn:oasis:names:tc:SAML:2.0:ac:classes:IAL2</saml:AuthnContextClassRef><saml:AuthnContextClassRef>urn:oasis:names:tc:SAML:2.0:ac:classes:IAL3</saml:AuthnContextClassRef></saml:AuthnContext>` |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.1kosmos.com/identity-verification/ial2-verification/saml.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
