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


---

# (Workaround) Support Kerberos authentication

# (Workaround) Support Kerberos authentication {#ariaid-title1}

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

A workaround is available for the SAML 2.0 integration that changes the authentication context from forms-based authentication to Windows-based authentication.

## Vorbereitungen

Role required: sso_config_admin, business_rule_admin, script_include_admin

## Warum und wann dieser Vorgang ausgeführt wird

Currently, the SAML 2 integration uses a PasswordProtectedTransport or "forms-based authentication" authentication context. This authentication context requires the IdP to present users with a form for authentication
credentials. With Kerberos, a SAML session is already active through an established Windows login, so the user does not need to authenticate with the IdP.

## Prozedur

1. Navigate to AllMulti-Provider SSOIdentity Providers.
2. Open the SAML2 Update1 IdP record.
3. Set the The AuthnContextClassRef method that we will be included in our SAML 2.0 AuthnRequest to the Identity Provider to one of the following:  

   |-|
   | <kbd class="ph userinput">urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport </kbd> (Default) |
   | <kbd class="ph userinput">urn:federation:authentication:windows</kbd> |
   [Tabelle : 1. AuthnContextClassRef method values]

   {#t_SupportKerberosAuthentication__table_kqd_rzg_cs}
4. Click Update.
{#t_SupportKerberosAuthentication__steps_z32_wyg_cs}