---
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


---

# Log in using Multi-Provider SSO

# Log in using Multi-Provider SSO {#ariaid-title1}

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

The recommended and most efficient method for users to log in using Multi-Provider
SSO is to use a specifically configured URL.

## Vorbereitungen

Role required: sso_config_admin, business_rule_admin, script_include_admin

## Warum und wann dieser Vorgang ausgeführt wird

After multi-provider SSO is configured, you can send a URL to your users with the
correct IdP in the parameter string. For example:

/login_with_sso.do?glide_sso_id=\<sys_id of the sso configuration\>

After a user successfully logs in to the IdP page, a cookie containing the IdP sys_id
is added to the browser. The next time the user attempts to log in, the system
redirects the user to log in to the IdP server, which automatically logs in to the
instance.

If a URL parameter is not set or the browser cache has been cleared, users can also
do the following:

## Prozedur

1. Click the Use external login link on the login page.  
   The external login page appears. Users can click Use local login to return to the standard login page.
2. Enter the value for the specified field on the user table that you configured in Multi-Provider SSO properties.  
   The user is redirected to the IdP server, where they log in.

## Ergebnisse

After users successfully log in to an IdP, they are automatically redirected to that
IdP whenever they attempt to access the instance. To have a user access a different
IdP, send the user a URL with the new IdP information in the parameter. The new IdP
overwrites the old IdP in the cookie if the user successfully logs in. If the user
does not log in successfully, the old IdP information is retained in the cookie.