Contents Now Platform Administration Previous Topic Next Topic Authentication Subscribe Log in to subscribe to topics and get notified when content changes. ... SAVE AS PDF Selected Topic Topic & Subtopics All Topics in Contents Share Authentication ServiceNow authentication validates the identity of a user who accesses an instance, and then authorizes the user to features that match the user's role or job function. Available authentication methods You can use several different methods to authenticate users. User credentials are matched to different saved credentials for each method. Note: The OKTA SSO plugin has been deprecated for the New York release. It is still available in Jakarta. Authentication methods Description Local database The username and password in their user record in the instance database. External Single Sign-on (SSO) The username and password configured in identity providers, which have a matching user account in the database. LDAP The username and password in their LDAP account, which has a matching user account in the database. OAuth 2.0 The username and password of OAuth identity provider, which has a matching user account in the database. Digest Token An encrypted digest of the username and password in the user record. Multifactor The username and password in the database and a passcode sent to the user's mobile device that has Google Authenticator installed. Note: You can use SAML and Digest Authentication through the Multiple Provider SSO application. External single sign-on (SSO)External SSO allows organizations to use several SSO identity providers (IdPs) to manage authentication as well as retain local database (basic) authentication.LDAP integrationAn LDAP integration allows your instance to use your existing LDAP server as the master source of user data.Authentication with SAMLThe Security Assertion Markup Language (SAML) is an XML-based standard for exchanging authentication and authorization data between security domains.Limit concurrent sessionsYou can limit the number of concurrent interactive sessions for a user or role on an instance across all nodes.OAuth 2.0OAuth 2.0 lets users access instance resources through external clients by obtaining a token rather than by entering login credentials with each resource request.Digest token authenticationThe digest token authentication passes user credentials and a digest token within an unencrypted HTTP header.Multifactor authentication (MFA)MFA, also known as two-step verification, is a security requirement that asserts a user enter more than one set of credentials to authenticate to an instance. Enable external authenticationYou can enable external authentication on your instance.Associating custom URLs to your instanceYou can enable your ServiceNow instance to be accessible from a company-branded or custom URL. On this page Send Feedback Previous Topic Next Topic
Authentication ServiceNow authentication validates the identity of a user who accesses an instance, and then authorizes the user to features that match the user's role or job function. Available authentication methods You can use several different methods to authenticate users. User credentials are matched to different saved credentials for each method. Note: The OKTA SSO plugin has been deprecated for the New York release. It is still available in Jakarta. Authentication methods Description Local database The username and password in their user record in the instance database. External Single Sign-on (SSO) The username and password configured in identity providers, which have a matching user account in the database. LDAP The username and password in their LDAP account, which has a matching user account in the database. OAuth 2.0 The username and password of OAuth identity provider, which has a matching user account in the database. Digest Token An encrypted digest of the username and password in the user record. Multifactor The username and password in the database and a passcode sent to the user's mobile device that has Google Authenticator installed. Note: You can use SAML and Digest Authentication through the Multiple Provider SSO application. External single sign-on (SSO)External SSO allows organizations to use several SSO identity providers (IdPs) to manage authentication as well as retain local database (basic) authentication.LDAP integrationAn LDAP integration allows your instance to use your existing LDAP server as the master source of user data.Authentication with SAMLThe Security Assertion Markup Language (SAML) is an XML-based standard for exchanging authentication and authorization data between security domains.Limit concurrent sessionsYou can limit the number of concurrent interactive sessions for a user or role on an instance across all nodes.OAuth 2.0OAuth 2.0 lets users access instance resources through external clients by obtaining a token rather than by entering login credentials with each resource request.Digest token authenticationThe digest token authentication passes user credentials and a digest token within an unencrypted HTTP header.Multifactor authentication (MFA)MFA, also known as two-step verification, is a security requirement that asserts a user enter more than one set of credentials to authenticate to an instance. Enable external authenticationYou can enable external authentication on your instance.Associating custom URLs to your instanceYou can enable your ServiceNow instance to be accessible from a company-branded or custom URL.
Authentication ServiceNow authentication validates the identity of a user who accesses an instance, and then authorizes the user to features that match the user's role or job function. Available authentication methods You can use several different methods to authenticate users. User credentials are matched to different saved credentials for each method. Note: The OKTA SSO plugin has been deprecated for the New York release. It is still available in Jakarta. Authentication methods Description Local database The username and password in their user record in the instance database. External Single Sign-on (SSO) The username and password configured in identity providers, which have a matching user account in the database. LDAP The username and password in their LDAP account, which has a matching user account in the database. OAuth 2.0 The username and password of OAuth identity provider, which has a matching user account in the database. Digest Token An encrypted digest of the username and password in the user record. Multifactor The username and password in the database and a passcode sent to the user's mobile device that has Google Authenticator installed. Note: You can use SAML and Digest Authentication through the Multiple Provider SSO application. External single sign-on (SSO)External SSO allows organizations to use several SSO identity providers (IdPs) to manage authentication as well as retain local database (basic) authentication.LDAP integrationAn LDAP integration allows your instance to use your existing LDAP server as the master source of user data.Authentication with SAMLThe Security Assertion Markup Language (SAML) is an XML-based standard for exchanging authentication and authorization data between security domains.Limit concurrent sessionsYou can limit the number of concurrent interactive sessions for a user or role on an instance across all nodes.OAuth 2.0OAuth 2.0 lets users access instance resources through external clients by obtaining a token rather than by entering login credentials with each resource request.Digest token authenticationThe digest token authentication passes user credentials and a digest token within an unencrypted HTTP header.Multifactor authentication (MFA)MFA, also known as two-step verification, is a security requirement that asserts a user enter more than one set of credentials to authenticate to an instance. Enable external authenticationYou can enable external authentication on your instance.Associating custom URLs to your instanceYou can enable your ServiceNow instance to be accessible from a company-branded or custom URL.
