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

  • 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 for more information.

New in the Yokohama release

Continuous Authentication
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
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

Multi-factor authentication (MFA) enforcement
MFA is mandated and is enforced to all the non-SSO login users accessing ServiceNow®.

Activation information

Authentication is a ServiceNow AI Platform product that is active by default.