Single Sign-On (SSO) allows users to access multiple applications with a single set of credentials. Security Assertion Markup Language (SAML) protocol is commonly used for SSO integrations between Okta and applications. However, some users may wonder if it is possible to integrate multiple SAML applications with the same metadata. This article will explain why it is not possible and what the solution is.

• SAML App Integrations

Each SAML application integration requires unique metadata. The metadata contains information about the application, such as the URLs for the Service Provider (SP), Assertion Consumer Service (ACS), and single logout service, as well as the entity ID and signing certificates. When configuring SAML applications in Okta, the metadata for each application must be unique to ensure proper communication between Okta and the application.

To integrate multiple SAML applications with Okta, follow the steps below:
 

1. Create a new SAML application for each application that needs to be integrated with Okta.
2. Obtain the metadata for each application. This can usually be found on the application's website or provided by the application vendor.
3. Configure the SAML application in Okta using the unique metadata for each application.
4. Test the SSO integration to ensure that it is working properly.
    

By creating a separate SAML application for each application that needs to be integrated with Okta and using unique metadata for each, it can be ensured that each SAML application integration works properly.