Technical Tip: An error message 'Related secret is busy for verifying' after certain SSH password changer attempts

Description

This article describes a solution when the following error message is prompted: ‘Related secret is busy verifying, recovering, or rotating. Alternatively, try clearing your last attempted credential in the secret (errCode=2)". Furthermore, it takes about 10 minutes for this error to be resolved whenever this occurs. 

Scope

FortiPAM v1.8.x.

Solution

1. Manually select password change in Secret Name, and the password is changed successfully.

2. Change the Secret template. Select 'Password Change' with the wrong password.

Note: 'Password change failed (Not Matched at step(3), reason: Expected string not found at step(3)), errCode=4'. The user purposely created an invalid input in the password changer to cause such an error.

3. Revert the previous Secret template. Select 'Password Change'. An error message is shown: 'Password change failed (Related secret is busy for verifying, recovering or rotating, or try to clear your last-attempted credential in the secret.), errCode=2. will appear on the next attempt.'

Note: Try changing the password again and again; it gives the same error message 'Related secret is busy for verifying'. Wait for 10 minutes and try again; the password change has been successful. The above test is purposely triggered to produce an error message: 'Related secret is busy for verifying.'.

The issue was fixed in FortiPAM v1.8.1. It is advisable to upgrade to v1.8.2 GA. 

Bug ID # 1250635: Secret gets into an abnormal status after certain SSH password changer steps are not matched.