Users are provisioned in three different methods within the tenant-manually adding them, Netskope Tools Directory Importer, or via System for Cross-domain Identity Management (SCIM). SCIM is an open standard designed to manage user identity information. It is possible to use all three methods to provision users to the tenant. However, it is recommended that only one method be used to avoid confusion.
As more and more resources migrate to the cloud, it makes sense to use an Identity Provider (IDP) which resides in the cloud as well. SCIM provides a defined schema for representing users and groups, and a RESTful API to run CRUD operations on those user and group resources.
This guide provides administrators the ability to migrate from the Netskope Tools Director Importer to SCIM, regardless of the service provider such as Okta or Ping.
Review each setting area below to note the users and organization units used. These will need to be reconfigured after migrating from OU’s to groups.
NOTE: Steering and client configurations will be the default tenant config until everything is mapped when using SCIM after the migration to SCIM.
Using SCIM at a cloud provider will provide an easier method to administer users or groups since it is not dependent on a tool which connects to directory services, wherever they may reside.
Please reach out if there are issues the migration as additional actions might need to be done if all of the users and/or groups are not removed from the UI.
In order to view this content, you will need to sign in to your account. Simply click the "Sign In" button belowSign In