---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Enable users to choose the identity provider for login

# Enable users to choose the identity provider for login {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

SSO federation support enables users to choose which IdP to log in to.

## Vorbereitungen

Role required: sso_config_admin, business_rule_admin, script_include_admin

## Warum und wann dieser Vorgang ausgeführt wird

SSO federations aggregate metadata from multiple IdPs and service providers, including your instance. Federations then publish the metadata as an XML file, which includes information like IdP names and IdP certificates.
Administrators can then instruct the instance to read the XML file and automatically populate the SSO Properties table with all the necessary IdP information.

## Prozedur

1. Navigate to AllMulti-Provider SSOFederation.
2. Click New.
3. Fill in the fields, as appropriate (see table).
4. Click Submit.
5. After you configure a federation, enable the Refresh SSO Metadata scheduled job, and then [configure the users who you want to access the federation IdPs](https://servicenow-prod.fluidtopics.net/nVyCSSpmu10NYxdOR4S7CA "Describes the different entities that can authenticate a user through the SAML multi-SSO."). Use the sys_ID of the federation record you just created.  
   Use the sys_ID of the federation record that you just created.  
   The instance populates the SSO properties table with the IdP information. When users who are configured to use the federation log in, they are redirected to the discovery service URL you configured. Then they select the IdP and provide the necessary credentials. Alternatively, you can send users a URL with the IdP in the parameter.{#t_AllowUsersToChooseTheLoginIdP__table_m42_2nw_fp__entry__2}

   | Field | Description |
   |-|-|
   | Name | Enter a descriptive name for the federation. |
   | Active | Select the check box to enable the instance to pull the XML file from the federation. |
   | Type | Select the type of authentication this federation supports. |
   | Discovery Service URL | Enter the URL of the discovery service for this federation. This is the site where users are directed to select an IdP and log in. |
   | Meta Data URL | Enter the URL of the XML file that holds the federation metadata. |
   | x509 Certificate | Select the federation certificate. |
   | Domain | Select the domain that the data will belong to. |
   [Tabelle : 1. Allowing users to choose the identity provider for login]

   {#t_AllowUsersToChooseTheLoginIdP__table_m42_2nw_fp}  
   Hinweis:  
   The InCommon federated identity management IdP is preconfigured.