The Egnyte Provisioner synchronizes users from your datastore to Egnyte. The behavior of each provisioning capability is described below.
You can configure these capabilities in the Configure provisioning step of the setup process.
Synchronizing existing users
PingFederate synchronizes users based on the Username
attribute in Egnyte. If a user already exists in your datastore and Egnyte, mapping this attribute correctly links the two records
together.
For example:
- In Egnyte, Janet's
Username
isbjensen@example.com
. - In your datastore, Janet's
mail
isbjensen@example.com
. - On the Attribute Mapping tab of your provisioning connection
configuration, you map the
Username
attribute tomail
. - When the provisioning connector runs, the datastore user is provisioned with a
Username
ofbjensen@example.com
. That matches Janet's existingUsername
in Egnyte, so her information in the datastore is synchronized to her Egnyte account.
User provisioning
- A user is added to the datastore group or filter that is targeted by the provisioning connector.
The Source Location tab of your provisioning connection configuration defines which users PingFederate targets for provisioning.
User updates
PingFederate updates users when a user attribute changes in your datastore.
The Attribute Mapping tab of your provisioning connection configuration defines which attributes PingFederate monitors for changes.
User deprovisioning
PingFederate deprovisions users when one of the following happens:
- A user is deleted from the user store.
- A user is disabled in the user store.
- A user is removed from the datastore group or filter that is targeted by the provisioning connector.