Queuing password changes
Bravura Pass can extend web-based password management by using the Password Manager service (idpm ) to queue password changes if the number of requests reaches a specific limit or to retry the change later if it failed.
Queuing failed password changes
You can use the S RESET TO PUSHPASS and A RESET TO PUSHPASS options to enable the automatic retrying (queuing) of failed web-based password changes.
S RESET TO PUSHPASS controls the behavior of the Change passwords (PSS) module and is set on the page. A RESET TO PUSHPASS controls the behavior of the Manage the system (PSA) module and is set on the page.
If your password policy enforces password history, failed password changes cannot be queued for automatic retry on target systems that are designated as synchronization triggers.
These settings have three possible values:
none | Bravura Pass behaves normally. Failed password changes must then be manually retried by logging into Bravura Pass and attempting the change at a later time, or through the use of a plugin. |
Manual | Users can select the accounts to be queued. If a password change failure occurs, users are notified on the password reset results page. The user may select accounts to queue by selecting the appropriate checkboxes under the Queue for automatic retry? column, and clicking the Queue failed changes button. Bravura Pass lists the target system and account IDs queued for automatic retry. |
Automatic | All failed password changes are queued for automatic retry. A message displays notifying the user that ”the failed password changes are queued and will automatically be retried”. |