![]() ![]() If you have your current ServiceNow app configured with Active Directory, you need to also copy and paste mappings for all attributes to be the same as your current app. Copy and paste mappings from your current Service Now - Eureka for all duplicated attributes, then click Save Mappings. ![]() Click Map Attributes, then go to Okta to ServiceNow UD.Note: If you have the Location attributes in your current Service Now - Eureka app, you need to add it to the new ServiceNow UD app as follows:Ĭlick Add Attribute, select the Location attribute, then click Save. Select the Provisioning tab and then Configure API Integration. ![]() See Determine your current ServiceNow configuration Select the same SIGN ON METHOD as your current ServiceNow - Eureka app instance, then click Done. In the Admin Console, go to Applications Applications.Įnter the Base URL for your ServiceNow tenant, then click Next. If you have custom mappings, these also need to be copied over.Ĭonfigure a new ServiceNow UD app instance You will have to copy these to your new ServiceNow UD app. Open the Profile Editor, locate your current ServiceNow app and check the current mappings. You can manually unassign such users after migration. If you have unassigned users from your existing ServiceNow app, but who are not actually deactivated on the ServiceNow side, these users would be auto-confirmed for the new ServiceNow UD app. If the Deactivation feature is disabled for your existing ServiceNow app, you may run into issues during user migration to your new ServiceNow UD instance. To migrate such users, they have to be manually confirmed. If you have users with updated profiles in ServiceNow, for example, an updated email address, these users cannot be auto-confirmed during import. If the Update user attributes feature is disabled for your existing ServiceNow app, you may have some unsynchronized users, which can be missed during migration. User sets username and password: In this case, following migration, end users must enter valid usernames and passwords they are using for the current ServiceNow SWA app.Īdministrator sets username, user sets password: In this case, after migration, end users must enter valid passwords they are using for the current ServiceNow SWA app. Okta recommends that you enable this feature before migration to avoid having to manually enter passwords for all migrated users. If the Sync Password feature is not enabled for your existing ServiceNow app, it means you may allow end-users to set their passwords depending upon the setting you select under Secure Web Authentication on the Sign On tab.Īdministrator sets username and password: In this case, you have to manually enter passwords for all migrated users. Enable all provisioning features if you want to manage all user's data from Okta: Enable the same features for your new ServiceNow UD app to avoid missing or overwriting user's data. Make note of the features that are enabled. Use the same value for your new ServiceNow UD app.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |