--- sourceDocument: brazil Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/delta-yokohama-brazil Release : - brazil ft:locale : - en-US ft:publication_title : - brazil Combined Product Files ft:clusterId : - delta3by bundleId : - delta3by --- # Combined Authentication release notes for upgrades from Yokohama to Brazil # Combined Authentication release notes for upgrades from Yokohama to Brazil {#ariaid-title1} Release version: Brazil Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 18 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 Yokohama to Brazil This consolidated release note summary guides ServiceNow customers through the Authentication product upgrades from Yokohama to Brazil releases. It highlights new features, changes, deprecations, and important upgrade tasks across multiple releases including Yokohama, Zurich, Australia, and Brazil. Authentication remains an active ServiceNow AI Platform product by default with no additional activation required. Show full answer Show less ## Key Features * **Continuous Authentication:** Enforce step-up or re-authentication before accessing sensitive or high-privilege information (Yokohama). * **OAuth Enhancements:** Support for multiple OAuth grant types including Authorization Code, Resource Owner Password Credential, SAML Bearer, JWT Bearer for MID Server outbound integrations; expanded client secret length; JWKS URL support for automatic JWT public key management; and JWT signing algorithms (ES and RS variants) (Yokohama, Zurich, Australia). * **Multi-factor Authentication (MFA):** Enforced by default for non-SSO users with a new MFA Dashboard for user enrollment insights, and MFA Guided Setup for streamlined configuration (Zurich). * **Machine Identity Console:** Simplifies inbound integration configuration for secure connections (Zurich). * **AI Voice Service Authentication:** Enable caller authentication via various factors including Email OTP, Knowledge-Based Authentication (KBA) with voice input support, and step-up authentication challenges before sensitive operations (Australia, Brazil). * **Policy-based Login Experience (Brazil):** Identifier-first login framework lets you tailor login methods based on user context (e.g., username or email) to simplify user experience. * **SAML Certificate Expiry Notifications:** Home page banner alerts warn administrators before signing or encryption certificates expire, with direct links to remediation actions (Brazil). * **Workload Identity Federation:** Authenticate outbound connections to Microsoft Azure and Google Cloud Platform using federated identity, eliminating the need for stored client secrets (Brazil). * **Domain-Level Certificate Validation Exclusion:** Configure SSL/TLS validation policies per outbound endpoint to customize hostname verification, certificate chain validation, and revocation checking without impacting global settings (Brazil). * **Basic Authentication Restrictions:** Limit Basic Auth access using an allowlist and a tracking period to identify legitimate users before enforcing restrictions (Brazil). * **Trusted External Authorization for MCP Clients:** Register external OIDC providers to validate tokens locally without relying on ServiceNow authorization servers, enhancing security for MCP Server integrations (Brazil). * **Granular Admin Roles:** Assign specific admin privileges for Authentication configurations without granting full admin rights, improving governance (Australia). * **Web Embeddables Security:** Secure web components embedded in third-party portals to enforce authentication (Australia). * **Enhanced SSO Experience:** Improved login/logout flows with active IdP displays, user group assignment during auto-provisioning, and detailed login failure feedback (Zurich). * **FIDO2 MFA Support:** Enforce hardware key or biometric second-factor authentication (Zurich). ## Changes * MFA enforcement is now mandatory for all non-SSO users (Yokohama). * The Coral theme is the new default for portal, web, and mobile experiences offering a modern, brand-neutral, and accessible UI with dark mode options (Zurich, Australia, Brazil). * Refined handling of the maxage parameter in authentication requests to align with OpenID Connect specifications, ensuring reauthentication after a specified time (Brazil). * Improvements to OAuth token handling and provider name management to enhance monitoring and security (Yokohama, Zurich). ## Deprecations and Removals * Legacy OAuth API endpoints for external clients and certain inbound integration configurations are deprecated due to new simplified inbound integration setups in the Machine Identity Console (Zurich, Australia). * The property glide.login.noblankpassword is deprecated as it no longer affects login behavior (Australia). * No significant removals or deprecations specific to the Brazil release. ## Upgrade Considerations and Activation Authentication is active by default across all releases; no activation steps are necessary. Customers should review pre- and post-upgrade tasks to ensure smooth transition. ## Practical Benefits for ServiceNow Customers * **Security Enhancement:** Enforced MFA and continuous authentication improve protection for high-value data and sensitive transactions. * **Improved User Experience:** Policy-based login and enhanced SSO flows simplify access while maintaining security. * **Integration Flexibility:** Expanded OAuth grant types, workload identity federation, and trusted external authorization servers enable secure, seamless integrations with cloud and third-party services. * **Compliance and Monitoring:** MFA dashboards, certificate expiry alerts, and granular admin roles support better governance and compliance management. * **AI Voice Agent Security:** Multiple authentication factors and step-up challenges protect sensitive voice Consolidated page of all release notes for Authentication from Yokohama to Brazil. ## 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 Yokohama to Brazil. 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 Brazil Before you upgrade to Brazil, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-authentication-summary__entry__2} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## New features Between your current release family and Brazil, new features were introduced for Authentication. {#dfrn3-authentication-summary__entry__12} | Release | Release notes | |-|-| | 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. | | Zurich | [Machine Identity Console](https://www.servicenow.com/docs/access?context=machine-identity-console&family=zurich&ft:locale=en-US) : Manage your inbound integration with ServiceNow's Machine Identity Console. Inbound integration in Machine Identity Console provides a simplified configuration experience for your inbound integrations. [Multi-factor Authentication dashboard](https://www.servicenow.com/docs/access?context=mfa-dashboard&family=zurich&ft:locale=en-US) : Use the new MFA Dashboard to understand insights such as MFA user enrollment, privileged admins who haven't opted in to MFA, and compliance. You can verify that all users have MFA enabled for enhanced security with the help of the MFA Dashboard. [Multi-factor Authentication Guided Setup](https://www.servicenow.com/docs/access?context=mfa-guided-setup&family=zurich&ft:locale=en-US) : Use the new MFA Guided setup to configure multi-factor Authentication (MFA) for users who currently log in to ServiceNow with only a user name and password. This update enhances security by guiding administrators through the MFA setup process and verifying that all users are protected with an additional layer of authentication. [Attributes for OIDC](https://www.servicenow.com/docs/access?context=idp-attributes-oidc&family=zurich&ft:locale=en-US) : Use the Identity Provider (IDP) Attributes received from the OIDC response from the Identity Provider as a filter criteria for authentication. | | Australia | [Authentication factors for AI voice service](https://www.servicenow.com/docs/access?context=authentication-factors&family=australia&ft:locale=en-US) : Enable caller access to AI voice agents by configuring the required identification and authentication factors. [Web Embeddables](https://www.servicenow.com/docs/access?context=web-embeddables&family=australia&ft:locale=en-US) : Secure the web embeddables feature for authenticating the ServiceNow®'s web components that are used in third-party portals. [Granular admin roles](https://www.servicenow.com/docs/access?context=granular-admin-roles&family=australia&ft:locale=en-US) : The granular admin role enables developers and administrators to complete administrative configuration tasks for Authentication without requiring the full admin role. | | Brazil | [Policy-based login experience](https://www.servicenow.com/docs/access?context=next-gen-login-experience&family=brazil&ft:locale=en-US) : Use the Policy-based experience (identifier-first login) framework in the Authentication Console to craft login policies to simplify the login experience by presenting relevant login methods based on user context, such as username or email. [SAML certificate expiry notifications](https://www.servicenow.com/docs/access?context=c_SAML2.0WebBrowserSSOProfile&family=brazil&ft:locale=en-US) : Receive banner alerts on the home page when SAML SP signing or encryption keystores are approaching or past their expiry date. The instance displays two separate banners --- one for signing certificates and one for encryption certificates --- each linking to a dedicated customer action in Security Center. [Email OTP as an authentication factor](https://www.servicenow.com/docs/access?context=email-otp-authentication&family=brazil&ft:locale=en-US) : Use Email OTP as a standalone factor, a primary factor, or a secondary factor in AI voice agent authentication flows. When a caller reaches the voice agent, a one-time passcode is sent to their registered email address. The caller provides the passcode to complete authentication. Authenticate callers at the start of every call : Prompt callers for authentication or identification details at the start of every call, before the voice-only assistant responds to any request, using the Authenticate at the start of the call option on the Assistant Designer's Caller verification page. [Workload Identity Federation for Microsoft Azure and Google Cloud Platform](https://www.servicenow.com/docs/access?context=workload-identity-federation&family=brazil&ft:locale=en-US) : Authenticate outbound connections to Microsoft Azure and Google Cloud Platform using federated identity. [Domain-Level Certificate Validation Exclusion](https://www.servicenow.com/docs/access?context=outbound-certificate-policies&family=brazil&ft:locale=en-US) : Configure SSL/TLS certificate validation for individual outbound endpoints by creating outbound certificate policies, so you can adjust hostname verification, certificate chain validation, and revocation checking for a specific host without changing the global validation policy for every other endpoint. Issue ID tokens signed with RS256 : Issue ID tokens signed with the RSA SHA-256 algorithm (RS256) from the OpenID Provider. Use the ID Tokens in OAuth client applications to verify end-user identity. [Restrict Basic Authentication access with the Basic Auth Restriction page](https://www.servicenow.com/docs/access?context=basic-auth-restriction&family=brazil&ft:locale=en-US) : Use the Basic Auth Restriction page to strengthen instance security by limiting Basic Authentication access to a defined allowlist. Run the tracking period first to identify users currently relying on Basic Auth, then enable enforcement to block Basic Auth requests that don't match the allowlist. The allowlist covers Web Services Access Only (WSAO) users, SNC users, OAuth ROPC flow users, users presenting a valid OTP, and users granted the snc_basic_auth_api_access role. [Authenticate MCP clients with external authorization servers](https://www.servicenow.com/docs/access?context=mcp-3p-auth-concept&family=brazil&ft:locale=en-US) : Register an external authorization server as a trusted token issuer for the MCP Server by creating an OIDC Provider Configuration that identifies the provider's issuer URI and metadata endpoint. The MCP Server validates a token from a registered provider locally --- confirming the issuer is trusted, the signature is valid, the audience matches, and the token has not expired --- without depending on the ServiceNow authorization server. Tokens from issuers that aren't registered and active are rejected. [Step-up authentication for AI voice agents](https://www.servicenow.com/docs/access?context=step-up-authentication&family=brazil&ft:locale=en-US) : Require a caller who is already authenticated to complete an additional challenge before reaching an AI voice agent that handles a sensitive request, such as a password reset or access to bank account details. Select Okta Verify push notification, SMS verification code, or authenticator app time-based one-time password (TOTP) as the step-up factor on the Assistant Designer's Caller verification page. | [ ] ## Changes Between your current release family and Brazil, some changes were made to existing Authentication features. {#dfrn3-authentication-summary__entry__22} | Release | Release notes | |-|-| | 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®. | | Zurich | Coral theme : Coral is now the default theme for new portal, web, and mobile experiences with Next Experience or Core UI enabled. This theme provides a fresh look and feel, featuring brand-neutral illustrations to enhance your user experience. A dark theme option is available for web and mobile experiences. [Enhanced SSO login and logout experience](https://www.servicenow.com/docs/access?context=c_MultipleProviderSingleSignOn&family=zurich&ft:locale=en-US) : Use the enhanced SSO login and logout experience. Enhancement includes: * Display of active SAML and OIDC Identity Providers (IdPs) on the ServiceNow platform and portal login pages. * Assign users to specific groups during SAML and OIDC auto-provisioning. * Set up OIDC with the same well-known URL. The OIDC configurations can use the same well-known URL of the IdPs for multiple SSO records. * Display login failure reasons to the users who logged out of ServiceNow due to session expiry or other reasons. Use the login link on the external logout page to again log in to ServiceNow in case of successful logout. * Display of a generic error message for unsuccessful single log out. * Enhanced email notifications for SAML certificate and Encryption Key store update. [FIDO2 as an MFA factor](https://www.servicenow.com/docs/access?context=mfa-with-fido&family=zurich&ft:locale=en-US) : Use the FIDO factor policy to enforce FIDO (Hardware key or Biometric as second factor for authentication) as second factor authentication to users who attempt to log in to the instance. [OAuth integrations](https://www.servicenow.com/docs/access?context=oauth-inbound-and-outbound&family=zurich&ft:locale=en-US) : Configure OAuth integration that includes the following enhancements: * You can provide a maximum client secret length up to 4096 characters to meet security requirements of the third-party systems. * You can provide a JSON Web Key Set (JWKS) URL to automatically manage and update the public key for JSON Web Tokens (JWT) signature validation. * You can request OAuth tokens using the JWT grant type signed with Elliptic Curve Digital Signature Algorithm (ES) signing algorithms, including ES256, ES384, and ES512, for inbound JSON Web Tokens (JWT). It also supports RS256, RS384, RS512, HS256, HS384, and HS512. * You can customize the JWT ID (JTI) claim name in both inbound OpenID Connect (OIDC) and JWT Bearer flows. | | Australia | [OAuth enhancements](https://www.servicenow.com/docs/access?context=api-inbound-and-outbound&family=australia&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. | | Brazil | SAML certificate expiry notification : Receive more timely alerts --- the SAML certificate expiry notification triggers earlier and includes additional detail about affected keystores. Max age parameter handling : Set the max_age parameter in an authentication request to require that the end-user has authenticated within a specified number of seconds. When the elapsed time since the last authentication exceeds max_age, the Authorization Server reauthenticates the end-user. The max_age implementation has been refined to align with the OpenID Connect Core 1.0 specification. KBA for AI voice service : Use the KBA setup to configure Knowledge-Based Authentication (KBA) for the voice channel. Choose from base system questions at both the identification level and the authentication level. AI voice service mappings are populated automatically from your Assistant Designer selection, so manually mapping voice services is no longer a mandatory step in the KBA setup. | [ ] ## Removed Between your current release family and Brazil, some Authentication features or functionality were removed. {#dfrn3-authentication-summary__entry__32} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Deprecations Between your current release family and Brazil, some Authentication features or functionality were deprecated. {#dfrn3-authentication-summary__entry__42} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | * OAuth API endpoint for external clients * OAuth JWT API endpoint for external clients * OIDC provider to verify ID tokens | | Australia | * Due to the launch of new simplified inbound integration configuration in Machine Identity Console, the following inbound integrations configurations in the Application registry page are deprecated: * OAuth API endpoint for external clients * OAuth JWT API endpoint for external clients * OIDC provider to verify ID tokens * The (glide.login.no_blank_password) property is deprecated, since the property is no longer used and changing this property value doesn't effect login behavior. * OAuth API endpoint for external clients * OAuth JWT API endpoint for external clients * OIDC provider to verify ID tokens | | Brazil | No updates for this release. | [ ] ## Activation information Review information on how to activate Authentication. {#dfrn3-authentication-summary__entry__52} | Release | Release notes | |-|-| | Yokohama | Activation information : Authentication is a ServiceNow AI Platform product that is active by default. | | Zurich | Activation information : Authentication is a ServiceNow AI Platform product that is active by default. | | Australia | Activation information : Authentication is a ServiceNow AI Platform product that is active by default. | | Brazil | 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__62} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | | Brazil | 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__72} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | | Brazil | 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__82} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | Accessibility information : Coral theme : Coral is now the default theme for new portal, web, and mobile experiences with Next Experience or Core UI enabled. This theme provides a fresh look and feel, featuring brand-neutral illustrations to enhance your user experience. A dark theme option is available for web and mobile experiences. | | Brazil | Accessibility information : Coral theme : Coral is the default theme for new portal, web, and mobile experiences with Next Experience or Core UI enabled. This theme uses brand-neutral illustrations. A dark theme option is available for web and mobile experiences. | [ ] ## Localization information If there are specific localization considerations for Authentication we have noted them here. {#dfrn3-authentication-summary__entry__92} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Highlight information If there are specific highlight considerations for Authentication we have noted them here. {#dfrn3-authentication-summary__entry__102} | Release | Release notes | |-|-| | 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. | | Zurich | [Zurich Patch 10](https://www.servicenow.com/docs/access?context=zurich-patch-10&family=zurich&ft:locale=en-US) [Knowledge-based factor enhancement for AI voice service](https://www.servicenow.com/docs/access?context=knowledge-based-authentication&family=zurich&ft:locale=en-US) : Following are the knowledge-based authentication (KBA) enhancements: * Email OTP as an authentication factor for AI voice service: Use Email OTP as a standalone factor, a primary factor, or a secondary factor in AI voice agent authentication flows. When a caller reaches the voice agent, a one-time password is sent to their registered email address. The caller provides the password to complete authentication. * KBA for AI voice service: Use the KBA setup to configure Knowledge-Based Authentication (KBA) for the voice channel. Choose from base system questions at both the identification level and the authentication level. AI voice service mappings are populated automatically from your Assistant Designer selection, so manually mapping voice services is no longer a mandatory step in the KBA setup. * Authenticate callers at the start of every call: Prompt callers for authentication or identification details at the start of every call, before the voice-only assistant responds to any request, using the Authenticate at the start of the call option on the Assistant Designer's Caller verification page. [Zurich Patch 4](https://www.servicenow.com/docs/access?context=zurich-patch-4&family=zurich&ft:locale=en-US) [Authentication factors for AI voice service](https://www.servicenow.com/docs/access?context=authentication-factors&family=zurich&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=zurich&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. [Zurich Patch 3](https://www.servicenow.com/docs/access?context=zurich-patch-1&family=zurich&ft:locale=en-US) [Provider name for Inbound integrations](https://www.servicenow.com/docs/access?context=new-inbound-integrations&family=zurich&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=zurich&ft:locale=en-US). * For Basic authentication integrations, update the Provider name in the integration registration form. To know more about the integration registration form, see [View dashboard](https://www.servicenow.com/docs/access?context=view-inbound-api-integration-usage-dashboard&family=zurich&ft:locale=en-US). [Zurich Patch 1](https://www.servicenow.com/docs/access?context=zurich-patch-1&family=zurich&ft:locale=en-US) OAuth token enhancement : Use Opaque or JWT token option for your inbound integration endpoints. Zurich * Experience the new Inbound integration configuration in the Machine Identity Console. * Use the new MFA Dashboard to understand insights such as MFA user enrollment, privileged admins who haven't opted in to MFA, and compliance. * Use the FIDO factor policy to enforce FIDO-based authentication. * Use the enhanced SSO login and logout experience. * Configure the authentication policies to restrict access, reduce roles, or enforce MFA based on Identity Provider (IdP) attributes that are received from the OIDC response. See [Authentication](https://www.servicenow.com/docs/access?context=c_Authentication&family=zurich&ft:locale=en-US) for more information. | | Australia | [Australia Patch 7](https://www.servicenow.com/docs/access?context=australia-patch-7&family=australia&ft:locale=en-US) [Step-up authentication for AI voice agents](https://www.servicenow.com/docs/access?context=step-up-authentication&family=australia&ft:locale=en-US) : Require a caller who is already authenticated to complete an additional challenge before reaching an AI voice agent that handles a sensitive request, such as a password reset or access to bank account details. Select Okta Verify push notification, SMS verification code, or authenticator app time-based one-time password (TOTP) as the step-up factor on the Assistant Designer's Caller verification page. [Australia Patch 6](https://www.servicenow.com/docs/access?context=australia-patch-6&family=australia&ft:locale=en-US) [Human-assisted SMS OTP](https://www.servicenow.com/docs/access?context=human-assisted-sms-otp&family=australia&ft:locale=en-US) : Human-assisted SMS OTP lets a human agent verify an end user's identity by sending a one-time passcode via SMS during a live interaction. The agent initiates OTP generation and validation through the platform's scriptable APIs, and the consuming application (for example, CSM or FSO workspace) handles the agent-facing workflow and user interface. [Australia Patch 6](https://www.servicenow.com/docs/access?context=australia-patch-6&family=australia&ft:locale=en-US) [Human-assisted SMS OTP](https://www.servicenow.com/docs/access?context=human-assisted-sms-otp&family=australia&ft:locale=en-US) : Human-assisted SMS OTP lets a human agent verify an end user's identity by sending a one-time passcode via SMS during a live interaction. The agent initiates OTP generation and validation through the platform's scriptable APIs, and the consuming application (for example, CSM or FSO workspace) handles the agent-facing workflow and user interface. [Australia Patch 3](https://www.servicenow.com/docs/access?context=australia-patch-3&family=australia&ft:locale=en-US) [Authentication factors enhancement for AI voice service](https://www.servicenow.com/docs/access?context=explore-authentication-factors&family=australia&ft:locale=en-US) : Following are the authentication factors enhancements: * Email OTP as an authentication factor for AI voice service: Use Email OTP as a standalone factor, a primary factor, or a secondary factor in AI voice agent authentication flows. When a caller reaches the voice agent, a one-time password is sent to their registered email address. The caller provides the password to complete authentication. * KBA for AI voice service: Use the KBA setup to configure Knowledge-Based Authentication (KBA) for the voice channel. Choose from base system questions at both the identification level and the authentication level. AI voice service mappings are populated automatically from your Assistant Designer selection, so manually mapping voice services is no longer a mandatory step in the KBA setup. * Authenticate callers at the start of every call: Prompt callers for authentication or identification details at the start of every call, before the voice-only assistant responds to any request. Use the Authenticate at the start of the call option on the Assistant Designer's Caller verification page. [Australia Patch 1](https://www.servicenow.com/docs/access?context=australia-patch-1&family=australia&ft:locale=en-US) [Knowledge-based factor enhancement for AI voice service](https://www.servicenow.com/docs/access?context=knowledge-based-authentication&family=australia&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=australia&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=australia&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. Australia * Enable caller access to AI voice agents by configuring the required identification and authentication factors. * Secure the web embeddables feature for authenticating the ServiceNow®'s web components that are used in third-party portals. * Use the granular roles to complete administrative configuration tasks for Authentication without requiring the full admin role. * Use the enhanced Auth Scope for your Inbound Integrations. See [Authentication](https://www.servicenow.com/docs/access?context=c_Authentication&family=australia&ft:locale=en-US) for more information. | | Brazil | * Require a caller who is already authenticated to complete an additional challenge before reaching an AI voice agent that handles a sensitive request, such as a password reset or access to bank account details. * Simplify the login experience by crafting login policies that present relevant methods based on user context with the Policy-based experience - Identifier-first login experience. * Act before SSO is disrupted with home page banner alerts when SAML SP signing or encryption keystores are nearing or past expiry. * Authenticate callers in AI voice agent sessions using a one-time passcode delivered to a registered email address, as a standalone, primary, or secondary factor. * Connect ServiceNow to Microsoft Azure and Google Cloud Platform without storing or rotating client secrets, using federated identity based on signed JWTs. * Issue ID Tokens signed with RS256 from the ServiceNow OpenID Provider to give OAuth client applications a way to verify end-user identity. * Restrict Basic Authentication access on the instance to a defined set of trusted scenarios, with a tracking period to identify legitimate users before enforcement begins. * Configure SSL/TLS certificate validation for individual outbound endpoints by creating outbound certificate policies, so you can adjust hostname verification, certificate chain validation, and revocation checking for a specific host without changing the global validation policy for every other endpoint. * Register an external authorization server --- such as Microsoft Entra ID or Okta --- as a trusted token issuer for the MCP Server, so MCP clients can authenticate using tokens from your enterprise identity provider. See [Authentication](https://www.servicenow.com/docs/access?context=c_Authentication&family=brazil&ft:locale=en-US) for more information. | [ ]