Token-based authentication can be used in ServiceNow when consuming REST API.

Token-based authentication can be used in ServiceNow when consuming REST API.

• A. True
• B. False
• C. Only for SOAP APIs
• D. Not supported

Answer: (A)

Token-based authentication uses a token (such as an OAuth 2.0 access token) as proof of identity rather than a password. In ServiceNow you can configure outbound REST integrations to use OAuth 2.0 or other token-based schemes, obtaining an access token from an authorization server and sending it with each request (typically in the Authorization header as a Bearer token). This is a standard, supported way to secure REST API calls from ServiceNow, including server-to-server integrations via client credentials flow. So the statement is true: token-based authentication can be used when consuming REST APIs in ServiceNow.

Token-based authentication uses a token (such as an OAuth 2.0 access token) as proof of identity rather than a password. In ServiceNow you can configure outbound REST integrations to use OAuth 2.0 or other token-based schemes, obtaining an access token from an authorization server and sending it with each request (typically in the Authorization header as a Bearer token). This is a standard, supported way to secure REST API calls from ServiceNow, including server-to-server integrations via client credentials flow. So the statement is true: token-based authentication can be used when consuming REST APIs in ServiceNow.