User and group management

The not used in this IK links users and groups from the data store to not used in this IK. The behavior of each provisioning capability is described below.

Synchronizing existing users

By default, the provisioning connector synchronizes based on the userName attribute in not used in this IK. You can change the default mapping in Creating a provisioning connection.

For example:

In not used in this IK, Janet’s userName is jsmith.
In your data store, Janet’s sAMAccountName is jsmith.
On the Attribute Mapping tab of your PingFederate channel configuration, you map the userName attribute to sAMAccountName.
When the provisioning connector runs, the data store user is provisioned with a userName of jsmith. That matches Janet’s existing userName in not used in this IK, so her information in the data store is synchronized to her not used in this IK account.

User provisioning

Triggered by either of the following:

A user is added to the data store group or filter that is targeted by the provisioning connector.
A user with "disabled" status is added to the data store group or filter that is targeted by the provisioning connector, and the Provision disabled users provisioning option is enabled.

The target is determined by the Source Location tab in the provisioning connector configuration.

User updates

Triggered when a change occurs to a user attribute that is mapped in the provisioning connector configuration, such as an attribute change or the user being re-enabled from a disabled status.

User deprovisioning

Triggered by any of the following:

A user is deleted from the user store.
A user is disabled in the user store.
A user is removed from the data store group or filter that is targeted by the provisioning connector.

The Remove User Action setting in the connection configuration determines whether the deprovisioning action disables or deletes the user.

Synchronizing existing groups

The provisioning connector synchronizes groups from the data store to not used in this IK based on the group name.

For example:

In not used in this IK, there is a group is named Accounting.
In your data store, there is a group with a CN of Accounting.
When the provisioning connector runs, the two groups are synchronized.

Group provisioning

Triggered when a group is added to the data store filter that is targeted by the provisioning connector.

The target is determined by the Source Location tab in the provisioning connector configuration.

Group name updates

Renaming the group in the data store will trigger PingFederate to rename the group in not used in this IK.

Group membership updates

Changing group memberships through the group’s properties or a user’s properties will trigger PingFederate to update the group membership in not used in this IK.

Group memberships in the data store overwrite the group memberships in not used in this IK.

Group deletion