--- sourceDocument: Yokohama Release Notes sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/release-notes Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama Release Notes ft:clusterId : - rn bundleId : - rn --- # Authentication release notes # Authentication release notes {#ariaid-title1} Release version: Yokohama Updated January 30, 2025 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read The ServiceNow® Authentication application supports many authentication mechanisms that enable you to validate the identity of users. Authentication was enhanced and updated in the Yokohama release. ## Authentication highlights for the Yokohama release {#authentication-rn__authentication-rn-highlights} [Yokohama Patch 13](https://servicenow-prod.fluidtopics.net/3_Cmbeptw1ql3irGyAgBug "The Yokohama Patch 13 release contains important problem fixes.") [Knowledge-based factor enhancement for AI voice service](https://www.servicenow.com/docs/access?context=knowledge-based-authentication&version=yokohama&pubname=yokohama-platform-security&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&version=yokohama&pubname=yokohama-platform-security&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&version=yokohama&pubname=yokohama-platform-security&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. {#authentication-rn__ul_pzp_jlx_l3c} [Yokohama Patch 11](https://servicenow-prod.fluidtopics.net/o~Ty6nl6ETxZAE_DIVoJJw "The Yokohama Patch 11 release contains important problem fixes.") [Authentication factors for AI voice service](https://www.servicenow.com/docs/access?context=authentication-factors&version=yokohama&pubname=yokohama-platform-security&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&version=yokohama&pubname=yokohama-platform-security&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. {#authentication-rn__ul_fds_b2d_hhc} Provider name for Inbound integrations : 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&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US). * For Basic authentication integrations, update the Provider name in the integration registration form. {#authentication-rn__ul_cb4_1hw_khc} [Yokohama Patch 7](https://servicenow-prod.fluidtopics.net/Gs2iWPbHpHMxHq8yOoBAsQ "The Yokohama Patch 7 release contains important problem fixes.") 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. {#authentication-rn__ul_vjd_2tz_fvb} See [Authentication](https://www.servicenow.com/docs/access?context=c_Authentication&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US) for more information.{#authentication-rn__authentication-rn-highlights-5} ## New in the Yokohama release {#authentication-rn__authentication-rn-new-features} [Continuous Authentication](https://www.servicenow.com/docs/access?context=ca-homepage&version=yokohama&pubname=yokohama-platform-security&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&version=yokohama&pubname=yokohama-platform-security&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. ## Changed in this release {#authentication-rn__authentication-rn-changed-features} [Multi-factor Authentication enforcement](https://www.servicenow.com/docs/access?context=mfa-enforcement&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US) : MFA is mandated and is enforced to all the non-SSO login users accessing ServiceNow®. ## Activation information {#authentication-rn__authentication-rn-activation} Authentication is a ServiceNow AI Platform product that is active by default.{#authentication-rn__authentication-rn-activation-1} ## Related ServiceNow applications and features {#authentication-rn__authentication-rn-related-apps} [Secure your instance](https://www.servicenow.com/docs/access?context=platsec-landing&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US) : Platform Security is built into all levels of the ServiceNow AI Platform. Implement the security features that are appropriate for your organization. Manage failed logins and encrypted password protection, access control rules, and audit logs.