--- sourceDocument: australia Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/australia/delta-zurich-australia Release : - australia ft:locale : - en-US ft:publication_title : - australia Combined Product Files ft:clusterId : - delta3az bundleId : - delta3az --- # Combined Authentication release notes for upgrades from Zurich to Australia # Combined Authentication release notes for upgrades from Zurich to Australia {#ariaid-title1} Release version: Australia Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 10 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 Zurich to Australia This consolidated release note provides ServiceNow customers with a comprehensive view of Authentication feature updates, changes, deprecations, and enhancements when upgrading from the Zurich release to Australia. It serves as a practical guide to prepare for the upgrade by outlining what new capabilities are available, what existing features have changed, and which functionalities are deprecated or removed. Show full answer Show less ## Key Features * **Machine Identity Console:** Simplifies inbound integration configuration with ServiceNow's Machine Identity Console, streamlining setup and management. * **Multi-factor Authentication (MFA) Enhancements:** Introduction of an MFA Dashboard for monitoring user enrollment and compliance, along with a Guided Setup to help administrators enforce MFA for all users. * **OIDC Attribute Filtering:** Use Identity Provider (IdP) attributes from OIDC responses as criteria to control authentication policies. * **AI Voice Service Authentication:** New support for authentication factors including Email OTP, Knowledge-Based Authentication (KBA), and step-up authentication via Okta Verify, SMS, or authenticator apps to secure AI voice agent interactions. * **Web Embeddables Security:** Secure ServiceNow web components embedded in third-party portals to ensure authenticated access. * **Granular Admin Roles:** Developers and administrators can perform Authentication-related configuration tasks without needing full admin privileges, enhancing security and delegation. * **OAuth Improvements:** Support for longer client secrets, JWKS URL for automatic key management, JWT signing algorithms including ES and RS variants, customizable JWT ID claims, and enhanced token options such as Opaque or JWT tokens for inbound integrations. * **SSO Enhancements:** Improved login/logout flows with display of active SAML/OIDC Identity Providers, group assignment during auto-provisioning, and better error messaging for logout and login failures. * **FIDO2 MFA Factor:** Enforce hardware key or biometric-based second-factor authentication for stronger security compliance. ## Key Changes * **Coral Theme:** Coral is now the default user interface theme for portals, web, and mobile experiences, offering a fresh, brand-neutral design with optional dark mode. * **Deprecations:** Legacy inbound integration configurations for OAuth and OIDC in the Application Registry are deprecated in favor of the new Machine Identity Console setup. The property `glide.login.noblankpassword` is also deprecated as it no longer affects login behavior. * **Authentication Policies:** Enhanced ability to restrict access, reduce roles, or enforce MFA based on IdP attributes received from OIDC responses. ## Important Upgrade Considerations * Review and complete pre- and post-upgrade tasks as outlined to ensure a smooth transition to Australia release Authentication features. * Authentication remains active by default as a ServiceNow AI Platform product, requiring no additional activation steps. * No changes to browser requirements or localization were noted, maintaining consistency in user access and experience. ## Practical Benefits for ServiceNow Customers * Improved security posture through enhanced MFA capabilities, including guided setup and dashboard visibility. * Streamlined integration management with Machine Identity Console and OAuth enhancements for flexible and secure API integrations. * Better user experience with updated UI themes and SSO login/logout improvements. * Expanded authentication options for AI voice services, supporting more secure and user-friendly caller verification methods. * More granular administrative controls to delegate Authentication management securely without full admin access. Consolidated page of all release notes for Authentication from Zurich to Australia. ## 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 Zurich to Australia. 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 Australia Before you upgrade to Australia, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-authentication-summary__entry__2} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## New features Between your current release family and Australia, new features were introduced for Authentication. {#dfrn3-authentication-summary__entry__8} | Release | Release notes | |-|-| | 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. | [ ] ## Changes Between your current release family and Australia, some changes were made to existing Authentication features. {#dfrn3-authentication-summary__entry__14} | Release | Release notes | |-|-| | 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. | [ ] ## Removed Between your current release family and Australia, some Authentication features or functionality were removed. {#dfrn3-authentication-summary__entry__20} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Deprecations Between your current release family and Australia, some Authentication features or functionality were deprecated. {#dfrn3-authentication-summary__entry__26} | Release | Release notes | |-|-| | 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 | [ ] ## Activation information Review information on how to activate Authentication. {#dfrn3-authentication-summary__entry__32} | Release | Release notes | |-|-| | 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. | [ ] ## 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 | |-|-| | Zurich | No updates for this release. | | Australia | 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 | |-|-| | Zurich | No updates for this release. | | Australia | 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 | |-|-| | 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. | [ ] ## Localization information If there are specific localization considerations for Authentication we have noted them here. {#dfrn3-authentication-summary__entry__56} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | 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 | |-|-| | 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. | [ ]