ServiceNow Setup
Learn how to set up the ServiceNow connector
Connect to ServiceNow
Required permissions for setup
- The user setting up this data source must be a ServiceNow Admin.
Other prerequisites
-
Glean currently only indexes the following:
- Knowledge Articles
- Service Catalog items
- ITSM incidents (incident table)
- APM
- Business Applications (cmdb_ci_business_app table) and SPM demands
- epics and projects (dmn_demand, rm_epic, pm_project tables) in ServiceNow. To enable this, the ServiceNow admin creates a dedicated ServiceNow user with access only to the above doctypes.
-
All steps are to be done by a ServiceNow administrator. Note that the described steps are for the Tokyo release. If your instance is on a different ServiceNow release, the steps may differ slightly. If you have any questions, please contact Glean support.
-
Glean also supports additional configurations for custom ServiceNow URLs and custom Knowledge Article templates.
If applicable, please contact Glean support to set these up after completing the below steps.
-
Glean supports simple permissioning for ITSM, APM and SPM object types we support. Users with specific roles are granted access to all the documents. If you require a customized role, please reach out to Glean support.
1. Create a service account that Glean will use for fetching information from ServiceNow:
-
Navigate to Organization > Users and click New.
- Set User ID to
gleansearch
. - Ensure Web service access only is unchecked. This enables the user to log in via the ServiceNow portal to authorize the OAuth application.
- Set Time zone to
GMT
. This is required for new content updates to be picked up by Glean. - Leave the remaining fields as-is. Click Submit.
- Set User ID to
-
Click on the
gleansearch
user that was created. -
Click Roles > Edit… and add the following roles:
knowledge_admin
user_criteria_admin
user_admin
catalog_admin
snc_read_only
- Only add the following role if it exists in your instance:
snc_internal
- Add the following role if you want to index ITSM incidents as well:
itil
- Add the following role if you want to index APM Business Applications:
sn_apm.apm_user
- Add the following role if you want to index SPM documents (demands, projects and epics*):
it_demand_user
it_project_user
scrum_user
safe_scrum_user
Glean accesses only the following tables:
The
snc_read_only
role:- With the
snc_read_only
role, the user would not be able to log in to ServiceNow. The user needs write access to theoauth_credential
table during token creation. - After the OAuth flow has completed, you can assign the
snc_read_only
role to the user to prevent write access to any other tables during crawl.
2. Provide access to sys_audit_delete
table. This will help in faster updates to document permissions when identity data changes.
-
Create a new role:
read_access_sys_audit_delete
:- Navigate to User Administration > Roles.
- Click on New and enter the name as
read_access_sys_audit_delete
- Save.
-
Add an ACL rule that gives this role read access to the
sys_audit_delete
table:- Elevate role to security_admin to be able to create a new ACL.
- Navigate to System Security > Access Control (ACL).
- Click on New and enter the following details.
- Type:
record
- Operation:
read
- Name: Select the
sys_audit_delete
table - Add the new
read_access_sys_audit_delete
role under Requires role - Submit.
- Type:
-
Assign the new role
read_access_sys_audit_delete
togleansearch
user.
3. Configure an OAuth application that will provide access tokens to Glean acting as the above user:
- Navigate to System OAuth > Application Registry and click New.
- Click Create an OAuth API endpoint for external clients.
- Set Name to
Glean Search OAuth
. - Set Refresh Token Lifespan to
2,147,483,647
. - Set Access Token Lifespan to
86,400
. - Set Redirect URL to
https://<deployment-instance>-be.glean.com/instance/servicenow/oauth/verify_code
, where<deployment-instance>
is your instance’s deployment environment identifier. - Leave the remaining fields as-is. Click Submit.
4. Validate System Properties:
-
Navigate to the System Properties List (All > Enter sys_properties.list).
-
Identify and note the system property glide.knowman.apply_article_read_criteria and its value.
-
Identify and note the system property glide.knowman.block_access_with_no_user_criteria and its value.
-
Identify if you have Knowledge Article templates enabled and want to index template-based articles.
- Navigate to All > System Applications > All Available Applications > All
- Look for the plugin Knowledge Management Advanced (com.snc.knowledge_advanced) and check if it is enabled.
- You can learn more about knowledge article templates here.
5. Finally, enter ALL of the following information into the Glean admin console in the corresponding fields:
- Domain Name: Accepts domain or domain url. Note, the domain url should not include any http
prefixes, and should follow the format of
<domain>.service-now.com
. It is preferred to enter the domain url - User ID:
gleansearch
- OAuth Client ID: Client ID from the application in step 3.
- OAuth Client Secret: Client Secret from the application in step 3.
- Set the Apply article read criteria box to mirror the system property glide.knowman.apply_article_read_criteria.
- Set the Block access with no user criteria box to mirror the system property glide.knowman.block_access_with_no_user_criteria.
- If you have Knowledge Article templates enabled in your instance, check the Enable fetching template-based knowledge articles box.
- Tick the checkbox for the document types you want Glean to index Click Save in Glean. You’re all set!