You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It was observed that the recover via challenge questions option in the password-recovery-with-claims-options.jsp page in the accountrecoveryendpoint is not visible when triggering a password recovery flow with the challenge questions connector added in IS v7.0.0. The recovery flow that they follow is password recovery with multi claims as mentioned in [1].
It was also observed that upon one restart of WSO2 Identity Server the following REST API [2] that is being invoked in the above JSP page to determine if the recovery options are enabled or not returns only one recovery mode. Upon another server restart it returns another recovery mode, but not all recovery modes at the same time.
Describe the issue:
It was observed that the recover via challenge questions option in the
password-recovery-with-claims-options.jsp
page in the accountrecoveryendpoint is not visible when triggering a password recovery flow with the challenge questions connector added in IS v7.0.0. The recovery flow that they follow is password recovery with multi claims as mentioned in [1].It was also observed that upon one restart of WSO2 Identity Server the following REST API [2] that is being invoked in the above JSP page to determine if the recovery options are enabled or not returns only one recovery mode. Upon another server restart it returns another recovery mode, but not all recovery modes at the same time.
This needs to be fixed.
[1] - https://wso2docs.atlassian.net/wiki/spaces/IS570/pages/38176130/Password+Recovery#:~:text=REST%20APIs.-,Password%20recovery%20using%20multiple%20claims,-This%20feature%20allows
[2] - https://is.docs.wso2.com/en/latest/apis/user-account-recovery-v2-rest-api/#tag/Password-Recovery/operation/initiatePasswordRecovery
Optional Fields
Related issues:
Suggested labels:
The text was updated successfully, but these errors were encountered: