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


---

# Configure the digest properties for multi-provider single sign-on (SSO)

# Configure the digest properties for multi-provider single sign-on (SSO) {#ariaid-title1}

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

After enabling a digest installation exist script, configure properties for
multi-provider SSO.

## Vorbereitungen

Role required: adaptive_auth_admin, user_admin, sso_config_admin

## Warum und wann dieser Vorgang ausgeführt wird

If you are not using multi-provider single sign-on, configure standard single sign-on properties.

## Prozedur

1. Navigate to AllMulti-Provider SSOIdentity Providers.
2. Fill in the fields of Digest Properties form.

   | Option | Bezeichnung |
   | Name | Enter the name of the digest token. |
   | User | Enter the sys_user field that contains the matching data for the incoming header. |
   | HTTP Digest header name | Enter the HTTP header you generated. For example, `DE_USER`. |
   | HTTP header name | Enter the HTTP header you generated for your created digested token. For example, `SM_USER`. |
   | Secret Passphrase | Enter the secret key to use for encoding digest keys. For example, `32 or more characters`. |
   | Failed SSO Redirect field | Enter the URL to redirect users after a failed authentication. |
   | External logout redirect | Enter the URL to redirect users after a logout. |
   | Single Sign-on Script | Select MultiSSO_DigestedToken. |
   | Client Type | Choose the client type, based on the type of your client. Options:Iframe Embedded. Hinweis: If client type field is required for your configuration, you can edit the form and add the field. To know more, see [Configure client type for OAuth and SSO records](https://servicenow-prod.fluidtopics.net/CqJdg2mz1NR~jBr9hkChqg "Configure the Client Type field for OAuth and SSO record related configurations."). |
   |-|-|

   {#t_EnterDigestPropsMultiProviderSSO__choicetable_sf3_clr_xkb}
3. Click Update.
4. Set your Digested Token default to true.  
   When you set the default to true, this overwrites the system default digest token record associated to SSO. Once the first multi-provider SSO related IdP record activates, only records associated to multi-provider SSO will be used.

   Digest token records which exist in digest properties table can be
   individually called by appending the Sys_ID of the IdP. For example, a
   digest token record in the following authentication URL:
   https://\<instance_name\>.service-now.com/login_with_sso.do?glide_sso_id=\<sys_id_of_Digest_token_record\>\&SM_USER=\<user_name\>\&DE_USER=\<digested_token\>