Table of Contents

Uniform password for new accounts

(since IdM version 11.0.0)

The main goal of a uniform password for new accounts is to ensure that new identities will have the same password in newly created accounts.

This feature solves this scenario:

Without the use of the uniform password feature, after the completion of the mentioned scenario, ie. After completing the synchronization of contracts (automatic role recalculation), two new accounts A1 and A2 are created, each of which will contain a different password. The user will receive two notifications of the creation of a new account for each account separately.

If you use the uniform password feature, two accounts will also be created, but both will have the same password. The user will recevie only one notification about the creation of an account on systems S1 and S2.

How can be this feature enabled?

To ensure the same password for all new identity accounts created during synchronization, the systems on which we want to have the same password must be defined in the uniform password agenda.

That means: In the example above, we must ensure that systems S1 and S2 will be in the same active group of the uniform password.

This feature is active only during contract sync and for contracts where a identity state is changed:

This feature can be disabled by disabling the IdentityInitUniformPasswordProcessor initialization processor. This processor creates states of uniform password entities. Therefore, if you deactivate this processor, the entire uniform password feature will also be deactivated.

How to change password also in IdM?

For use same uniform password on systems and in the IdM, you have to enable this feature by the checkbox "Change password through IdM" on the uniform password detail.

How this feature works?

There is life cycle of this feature:

Future improvements

Support the use of the same transaction ID in dependent LRTs. This will allow HR and automatic recalculations to be used as dependent tasks.

Limitations

The uniform password feature works only under one transaction ID. It means you have to use recalculation of HR processes and automatic roles directly on the contract sync (checkboxes). Using depending tasks is not supported yet.

Main guide