ServiceNow
The ServiceNow connector is based on the REST connector. See the REST section for the full description of tabs, fields, and configuration options. Integration with ServiceNow enables system administrators to read and onboard access data (users, groups, roles, group memberships and role assignments) from ServiceNow into Omada Identity in order to perform recertification and/or assign access rights in ServiceNow.
In a provisioning context, ServiceNow connectivity works the same way as generic REST connectivity. The collector can retrieve information about users, groups and roles and the connector performs provisioning in the connected system.
ServiceNow connectivity supports all objects available in the ServiceNow REST API. However, only the following predefined queries and mappings are provided out of the box:
Supported objects and operations
| Resource | Possible operations |
|---|---|
| Users | Create, read, update and delete users. |
| Roles | Create, read, update, and delete resource assignments (role assignments) |
| Groups | Create, read, update, and delete resource assignments (group memberships) |
Minimum required permissions
You need to have access to ServiceNow REST API. You also need access to an existing ServiceNow account with the user_admin role. In this role, you will have the following required rights granted out of the box:
- Creation of User
- Assignment of Users to Groups
- Assignment of Roles to Users
Implementation notes
None.
Network requirements
The collector requires the port to the ServiceNow API endpoint to be open. The default port number for HTTPS is 443.
Prerequisites
Depending on the chosen authorization type (Basic Authorization or OAuth2 Password), you need to configure access to the entities required for the collector/connector to work on the ServiceNow side. To build a developer ServiceNow instance, see the ServiceNow development page.
📄️ Data import
Connection details
📄️ Data provisioning
Provisioning configuration
📄️ Migrating the REST-based collector to a .NET Query collector
Since Omada Identity 14.0.6 (Update 6) all collectors based on the generic REST collector have their Collector ID migrated from REST to Omada ODW NET Query. For the existing REST-based template collectors the migration process is performed during the update process, and it is transparent to the users.