The six methods available for user authentication in ServiceNow are:
Local Database – The user authenticates using a username and password stored in the instance
database.
Multifactor Authentication (MFA) – The user provides their username, password, and a passcode
(e.g., from Google Authenticator).
LDAP (Lightweight Directory Access Protocol) – The user authenticates using credentials stored in a
corporate LDAP directory.
SAML 2.0 (Security Assertion Markup Language) – The user is authenticated via an external SAML
Identity Provider (IdP).
OAuth 2.0 – The user authenticates via an OAuth identity provider (such as Google, Microsoft, or
Facebook).
Digest Token Authentication – The user authenticates using an encrypted token rather than directly
submitting a password.
Thus, the correct answer is:
✅ A, B, C, D, E, F
Comprehensive and Detailed In-Depth
ServiceNow supports multiple authentication methods to provide flexibility, security, and integration
capabilities with external identity providers.
Local Database Authentication:
ServiceNow stores usernames and passwords in the internal database.
Users authenticate directly with the instance.
This method is commonly used when no external authentication provider is configured.
Multifactor Authentication (MFA):
Enhances security by requiring two authentication factors:
Username and password (stored in the database).
Passcode from a registered device (such as Google Authenticator, Microsoft Authenticator).
MFA helps prevent unauthorized access even if credentials are compromised.
LDAP Authentication:
Allows users to authenticate against an external LDAP directory (such as Microsoft Active Directory).
The user must have a matching record in the ServiceNow user table ([sys_user]).
ServiceNow does not store passwords when using LDAP; it only validates credentials against the
directory.
SAML 2.0 Authentication:
Users authenticate via a SAML Identity Provider (IdP) such as Okta, Microsoft Azure AD, or Ping
Identity.
ServiceNow acts as a Service Provider (SP) and does not store passwords.
Provides Single Sign-On (SSO) capabilities.
OAuth 2.0 Authentication:
Allows authentication via OAuth providers (Google, Facebook, Microsoft, etc.).
Users do not need to store passwords in ServiceNow; instead, authentication is delegated to the
OAuth identity provider.
Digest Token Authentication:
Uses an encrypted token (instead of a plaintext password) to authenticate users.
Often used for API-based authentication or scenarios where passwords should not be transmitted
over the network.
Why These Are the Correct Methods?
Each method aligns with ServiceNow's authentication mechanisms as per official documentation.
ServiceNow supports a hybrid authentication approach, allowing multiple methods to coexist.
Reference from Certified System Administrator (CSA) Documentation:
ServiceNow Docs – Authentication Methods
https://docs.servicenow.com
ServiceNow Security Best Practices – Authentication & Access Controls
ServiceNow Developer Portal – SSO & OAuth Authentication
