Non-interactive sessions
-
- UpdatedAug 1, 2024
- 3 minutes to read
- Xanadu
- User Administration
The Non-Interactive Sessions plugin creates a distinction between interactive and non-interactive users.
- Interactive users
- New users added to the instance automatically become interactive users. Interactive users can perform the following actions:
- Use their user name and password to log in to the UI or a service portal.
- Connect to an instance from a URL that calls a UI page, form, or list, for example, https://<instance name>.service-now.com/incident.do.
- Connect with single sign-on, for example, digest authentication or a Security assertion markup language (SAML).
- Use their credentials to authorize SOAP connections if allowed by strict security.
- Use their credentials for other API connections such as WSDL, JSON, XML, or XSD without restriction.
- Non-interactive users
- Non-interactive users can only use their credentials to authorize API connections such as JSON, SOAP, and WSDL. They can’t log in to the ServiceNow UI. The strict security high security setting determines if non-interactive users are subject to Contextual Security Manager requirements.
Distinguishing between interactive and non-interactive users increases instance security by helping to ensure that users abide by the principle of least privilege.
Installed with Non-Interactive Sessions
- Adds a column titled Web Service Access Only [web_service_access_only] to the User [sys_user] table.
- Changes all existing users to be interactive users (web_service_access_only=false).
- Updates the User form to display the Web Service Access Only [web_service_access_only] field by default.
Create a non-interactive user for web services
Non-interactive users can only connect to a ServiceNow instance from an API protocol. Use this feature to set up user accounts for web service authentication purposes.
Before you begin
About this task
Non-interactive users can't log in to an instance or a service portal or connect through single-sign-on. They can be used as a MID Server user if they’re flagged as an Internal Integration User.
Procedure
Make a non-interactive user record interactive
Manually switch a non-interactive user to an interactive user.
Before you begin
Procedure
Update web service user accounts for strict security
If your instance requires strict security, add the soap role to any user accounts used for web services.
Before you begin
Procedure
- Navigate to .
- Select a web service user from the list.
- From the Roles related list, select Edit.
- Add soap to the Roles List.
- Select Save.
- Select Update.
Require authentication
You can specify whether non-interactive sessions require authentication from the High Security Settings module.
Before you begin
About this task
A non-interactive session bypasses the UI to connect to the instance at an API level. Typically, non-interactive sessions use set protocols such as JSON, SOAP, XSD, or WSDL. By default, all non-interactive sessions require authentication.
Procedure