Design self-service recovery with accountable verification
Password Self Help for IBM i is relevant when users need a supported way to recover access without an ordinary help-desk reset for every incident. The security question is how the person is verified and which actions they can take. Convenient recovery should not create an easier route around the organisation’s authentication policy.
Identify the user groups, existing identity processes and IBM i release. Confirm current verification and recovery methods supported by the selected configuration. Define who may enrol users, update recovery information and assist a user who cannot complete the self-service path.
Test failed verification and the assisted route
A pilot should cover successful recovery, an incorrect verification attempt and a user whose recovery information is unavailable. Establish limits, notifications and escalation in line with the approved customer policy. Use test accounts and avoid recording real recovery answers in general project documentation.
For UAE organisations with shift workers or overseas users, make the assisted process available within the contracted support arrangements rather than assuming a daytime office team is always reachable. Handover needs enrolment instructions, exception ownership and audit review. MMC can scope the configured recovery workflow; identity proofing policy and ongoing user administration remain customer decisions unless contracted.
Evidence to request for this scope
- Validate the selected identity-verification method using approved test accounts.
- Demonstrate failed verification, assisted recovery and relevant notifications.
- Record enrolment permissions, exception handling and the review of recovery activity.