> For the complete documentation index, see [llms.txt](https://docs.alemba.com/asm/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alemba.com/asm/asm-hermes/integrate/managing-integration/single-sign-on-using-saml/configuring-asm-for-single-sign-on.md).

# Configuring ASM for Single Sign-On

{% hint style="info" %}

### Before you start

You must have **Integration Setup** selected in the Admin tab of your **General Access security role**.
{% endhint %}

1. Select ≡ > **Admin** > **Integration**.

   Use Explorer to configure the Single Sign-On components:

   * Signing Certificates – enables you to configure Signing Certificates for use by the connector.
   * Identity Providers – enables you to add the metadata from the Identity Provider.
   * Service Providers – enables you to configure Service Providers for ASM.

## Service Provider Configuration

To configure your Service Provider and successfully connect to your chosen Identity Provider:

1. [**Export Identity Provider Metadata**](/asm/asm-hermes/integrate/managing-integration/single-sign-on-using-saml/exporting-service-provider-metadata.md) (XML) to create a federated trust between the Identity Provider and the Service Provider (ASM). The Microsoft ADFS metadata can be downloaded from **https\://\<adfs-server-name>/federationmetadata/2007-06/federationmetadata.xml**.
2. [Import Identity Provider Metadata](/asm/asm-hermes/integrate/managing-integration/single-sign-on-using-saml/importing-identity-provider-metadata.md).
3. [Install a Service Provider Signing Certificate.](/asm/asm-hermes/integrate/managing-integration/single-sign-on-using-saml/service-provider-signing-certificate.md)
4. [Configuring the Service Provider](/asm/asm-hermes/integrate/managing-integration/single-sign-on-using-saml/configuring-the-service-provider.md).
5. [Export Service Provider Metadata](/asm/asm-hermes/integrate/managing-integration/single-sign-on-using-saml/exporting-service-provider-metadata.md).
6. [Import Identity Provider Metadata](/asm/asm-hermes/integrate/managing-integration/single-sign-on-using-saml/importing-identity-provider-metadata.md).

{% hint style="warning" %}
Nano supports SSO for more than one system. However, when two instances of ASM are running on one system, but SSO has been applied to only one of them, Nano only logs in to the default system. In order for SSO to work correctly, the SSO needs to be enabled or disabled on both systems.
{% endhint %}


---

# 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.alemba.com/asm/asm-hermes/integrate/managing-integration/single-sign-on-using-saml/configuring-asm-for-single-sign-on.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.