--- sourceDocument: yokohama Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/delta-xanadu-yokohama Release : - yokohama ft:locale : - en-US ft:publication_title : - yokohama Combined Product Files ft:clusterId : - delta3yx bundleId : - delta3yx --- # Combined Authentication release notes for upgrades from Xanadu to Yokohama # Combined Authentication release notes for upgrades from Xanadu to Yokohama {#ariaid-title1} Release version: Yokohama Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Combined Authentication Release Notes for Upgrades from Xanadu to Yokohama This consolidated release notes document provides ServiceNow customers with essential information on upgrading Authentication features from the Xanadu release family to Yokohama. It highlights new features, changes, deprecations, and important upgrade considerations to help you prepare and manage the transition effectively. Show full answer Show less ## Key Features * **Continuous Authentication:** Yokohama introduces Continuous Authentication, requiring step-up or re-authentication before users access sensitive or high-privilege data, enhancing security controls. * **OAuth Grant Types for MID Server:** Support for Authorization code, resource owner password credential, SAML bearer, and JWT bearer OAuth grant types is now available for outbound integration requests via the MID Server. Personal Authentication is also supported through the MID Server, facilitating secure communication between ServiceNow instances and external systems. * **Multi-factor Authentication (MFA) Enhancements:** * Xanadu introduced support for FIDO2 authenticators, passkeys, biometrics, and hardware security keys as MFA factors without requiring an authenticator app. * Yokohama enforces MFA by default on all non-SSO login users, strengthening login security. * **AI Voice Service Enhancements (Yokohama Patches):** * Knowledge-based Authentication (KBA) now supports voice input for user responses and script-based validation against external systems. * Authentication factors can be configured for AI voice agents to enable caller access. * **OAuth Enhancements:** * Options to use Opaque or JWT tokens for inbound integration endpoints. * Scope-based API access restrictions for inbound integrations. * Improved configuration of OAuth parameters for outbound integrations via the OAuth Entity Resource tab. * Provider name field introduced for better identification and monitoring of inbound OAuth and Basic authentication integrations. ## Changes * Xanadu added new MFA factors that eliminate the need for an authenticator app setup. * Yokohama enforces MFA for all non-SSO logins to ServiceNow by default. ## Deprecations * The MultiSSO v1 plugin is deprecated; customers must upgrade to MultiSSO v2 for SAML 2.0 and OpenID Connect support. * The SAML 1.1 and OpenID SSO plugins are deprecated as identity providers have migrated to modern standards requiring MultiSSO v2. ## Important Upgrade Considerations * Authentication is active by default in both Xanadu and Yokohama releases. * Pre- and post-upgrade tasks should be reviewed and completed to ensure a smooth transition. * No additional browser, localization, or accessibility requirement changes have been introduced between Xanadu and Yokohama. ## Practical Impact for ServiceNow Customers Upgrading to Yokohama enhances your authentication security posture by enforcing MFA for non-SSO users and adding Continuous Authentication capabilities for sensitive data access. The expanded OAuth grant support via MID Server improves integration flexibility and security. Deprecation notices ensure you plan to migrate from older Single Sign-On plugins to supported MultiSSO v2 configurations, keeping your authentication infrastructure current and secure. Voice-enabled AI authentication improvements offer advanced user identification methods, particularly useful for voice agents. OAuth enhancements improve token management and API access control, aiding in secure integration monitoring and governance. Consolidated page of all release notes for Authentication from Xanadu to Yokohama. ## How to use this page To help you prepare for your upgrade, we have combined the cross-family Authentication release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Xanadu to Yokohama. Tip: If there were no updates for a release notes section in a certain family release, we included a short note for your reference. For example, if a product did not have any updates in Tokyo, the row says "No updates for this release." ## Important information for upgrading Authentication to Yokohama Before you upgrade to Yokohama, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-authentication-summary__entry__2} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | [ ] ## New features Between your current release family and Yokohama, new features were introduced for Authentication. {#dfrn3-authentication-summary__entry__8} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | [Continuous Authentication](https://www.servicenow.com/docs/access?context=ca-homepage&family=yokohama&ft:locale=en-US) : Use Continuous Authentication to require step-up authentication or re-authentication to the users before allowing access to sensitive or high-privilege information. [OAuth Grant Types for MID Server](https://www.servicenow.com/docs/access?context=oauth-outbound&family=yokohama&ft:locale=en-US) : Use the Authorization code, resource owner password credential, SAML bearer, and JWT bearer OAuth grant types of OAuth for outbound integration requests through the MID Server. Personal Auth is also supported through the MID server. MID Servers facilitate communication and data movement between a single ServiceNow® instance and external applications, data sources, and services. | [ ] ## Changes Between your current release family and Yokohama, some changes were made to existing Authentication features. {#dfrn3-authentication-summary__entry__14} | Release | Release notes | |-|-| | Xanadu | [Multi-factor Authentication (MFA)](https://www.servicenow.com/docs/access?context=mfa-config-landing&family=xanadu&ft:locale=en-US) : Use the FIDO2 authenticator, passkeys, biometric authenticators, and hardware security keys as multi-factor authentication (MFA) factors without requiring an authenticator app setup. | | Yokohama | [MFA enforcement](https://www.servicenow.com/docs/access?context=mfa-enforcement&family=yokohama&ft:locale=en-US) : MFA is mandated and is enforced to all the non-SSO login users accessing ServiceNow®. | [ ] ## Removed Between your current release family and Yokohama, some Authentication features or functionality were removed. {#dfrn3-authentication-summary__entry__20} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | [ ] ## Deprecations Between your current release family and Yokohama, some Authentication features or functionality were deprecated. {#dfrn3-authentication-summary__entry__26} | Release | Release notes | |-|-| | Xanadu | * The MultiSSO v1 plugin is deprecated. Upgrade to MutliSSO v2 from MultiSSO v1. For more information on how to upgrade to MultiSSO v2, refer to the knowledge article [MultiSSO v2 upgrade instructions \[KB9756504\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0756504) in the Now Support Knowledge Base. * The SAML 1.1 and SAML 1.1 Single Sign-On - Update 1 plugin is deprecated. The SAML-based identity providers (IdP) have already migrated to SAML 2.0. To use SAML 2.0, you must activate the MultiSSO v2 plugin and configure your identity provider. * The OpenID SSO plugin is deprecated. To use OpenID Connect (OIDC), you must activate the MultiSSO v2 and configure your OIDC-based identity provider. | | Yokohama | No updates for this release. | [ ] ## Activation information Review information on how to activate Authentication. {#dfrn3-authentication-summary__entry__32} | Release | Release notes | |-|-| | Xanadu | Authentication is a ServiceNow AI Platform product that is active by default. | | Yokohama | Activation information : Authentication is a ServiceNow AI Platform product that is active by default. | [ ] ## Additional requirements If any additional requirements were introduced or changed for Authentication we have noted them here. {#dfrn3-authentication-summary__entry__38} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | [ ] ## Browser requirements If any specific browser requirements were introduced or changed for Authentication we have noted them here. {#dfrn3-authentication-summary__entry__44} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | [ ] ## Accessibility information Review details on accessibility information for Authentication, such as specific requirements or compliance levels. {#dfrn3-authentication-summary__entry__50} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | [ ] ## Localization information If there are specific localization considerations for Authentication we have noted them here. {#dfrn3-authentication-summary__entry__56} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | [ ] ## Highlight information If there are specific highlight considerations for Authentication we have noted them here. {#dfrn3-authentication-summary__entry__62} | Release | Release notes | |-|-| | Xanadu | * Use the FIDO2 authenticator, passkeys, biometric authenticators, and hardware security keys as multi-factor authentication (MFA) factors without requiring an authenticator app setup. See [Authentication](https://www.servicenow.com/docs/access?context=c_Authentication&family=xanadu&ft:locale=en-US) for more information. | | Yokohama | [Yokohama Patch 13](https://www.servicenow.com/docs/access?context=yokohama-patch-13&family=yokohama&ft:locale=en-US) [Knowledge-based factor enhancement for AI voice service](https://www.servicenow.com/docs/access?context=knowledge-based-authentication&family=yokohama&ft:locale=en-US) : Following are the knowledge-based authentication (KBA) enhancements: * [Voice input support for KBA questions](https://www.servicenow.com/docs/access?context=create-knowledge-based-questions&family=yokohama&ft:locale=en-US): Configure KBA questions to support Voice as an input type, allowing users to provide spoken responses during identification and authentication. When Voice input is enabled, you can configure the expected format, provide examples, and optionally define a validation pattern using regular expressions. * [Script-based validation for external systems](https://www.servicenow.com/docs/access?context=create-knowledge-based-answers&family=yokohama&ft:locale=en-US): Configure KBA answers to validate that are created against external systems using custom scripts through the Script Configuration field. When set to Identification mode, you can write scoped scripts that validate caller identity against external authentication systems instead of internal ServiceNow AI Platform tables. [Yokohama Patch 11](https://www.servicenow.com/docs/access?context=yokohama-patch-11&family=yokohama&ft:locale=en-US) [Authentication factors for AI voice service](https://www.servicenow.com/docs/access?context=authentication-factors&family=yokohama&ft:locale=en-US) : Enable caller access to AI voice agents by configuring the required identification and authentication factors. [OAuth enhancements](https://www.servicenow.com/docs/access?context=api-inbound-and-outbound&family=yokohama&ft:locale=en-US) : Following are the OAuth enhancements: * Use Opaque or JWT token option for your inbound integration endpoints. * Use the Allow access only to APIs in selected scope option to enable access to the APIs that are explicitly listed in the selected scopes for your inbound integrations. * Use the OAuth Entity Resource tab for outbound integrations to configure resource parameters so they flow into the OAuth token request and are reflected in the token from your OAuth provider. [Provider name for Inbound integrations](https://www.servicenow.com/docs/access?context=new-inbound-integrations&family=yokohama&ft:locale=en-US) : Use the Provider name field to enter the details of your inbound integrations to distinguish between different inbound integrations on your ServiceNow AI Platform®. Update the Provider name in your API integrations to improve monitoring capabilities: * For OAuth integrations, update the provider name using the Provider name field. To know more, see [OAuth Inbound](https://www.servicenow.com/docs/access?context=oauth-inbound&family=yokohama&ft:locale=en-US). * For Basic authentication integrations, update the Provider name in the integration registration form. [Yokohama Patch 7](https://www.servicenow.com/docs/access?context=yokohama-patch-7&family=yokohama&ft:locale=en-US) OAuth token enhancement : Use Opaque or JWT token option for your inbound integration endpoints. Yokohama * Use Continuous Authentication to require step-up authentication or re-authentication to the users before allowing access to sensitive or high-privilege information. * Multi-factor Authentication (MFA) is enforced by default for all non-SSO login to ServiceNow®. * Use the Authorization code, resource owner password credential, SAML bearer, and JWT bearer OAuth grant types of OAuth for outbound integration requests through the MID Server. See [Authentication](https://www.servicenow.com/docs/access?context=c_Authentication&family=yokohama&ft:locale=en-US) for more information. | [ ]