Skip to content
ADFS integration with SAML 2.0 › Integrating SAML 2.0 with other features › SAML › Multi-Provider single sign-on \(SSO\) › Authentication › Access Management
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

(Workaround) Support Kerberos authentication

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

Before you begin

Role required: sso_config_admin, business_rule_admin, script_include_admin

About this task

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.

Procedure

  1. Navigate to All > Multi-Provider SSO > Identity 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:

`urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport` \(Default\)
`urn:federation:authentication:windows`
  1. Click Update.