Actions taken on users and groups in the identity source might not be reflected in the SaaS applications. The following table lists the actions in the identity sources and the corresponding action in the SaaS applications.
Table 11-2 Provisioning Actions
|
Identity Sources |
SaaS Applications |
|---|---|
|
Delete a user. |
Disables the SaaS account. |
|
Remove a user from the authorized group. |
Disables the SaaS account. |
|
Create a user. |
|
|
Move a user from out of the search context into the search context. |
Creates an account for the user in the SaaS applications, if the user is a member of a group with mapped SaaS authorizations. |
|
Move a user out of the search context. |
Disables the SaaS account. |
CloudAccess establishes identity based on an internal unique ID in the identity source, not based on the user name, and does not support recreating users with the same name unless they also have the same internal unique ID. Once a user has been mapped and provisioned, if you delete the user from the identity source and then recreate that user with the same name, you will not be able to cache and activate the user in CloudAccess or provision the user to SaaS applications. When CloudAccess is unable to cache users properly, the Cached User Status Bar indicates this status with a lower number of active users than cached users.