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
Describe the issue:
In the user account recover API v2, WSO2 IS is sending the confirmation code and flow confirmation code appended with a dot.
With the improvement done in #14808, users can use an OTP instead of UUID in the recovery flows and utilize it in the API based implementation such as mobile applications that will utilize REST API to confirm.
When the flow confirmation code and the confirmation code are appended, it is not to show only the confirmation code without string manipulation.
It is required to send the confirmation code without appending the confirmation code to the user in the recovery flow.
Expected behavior:
Only the confirmation code should send in the email. Flow confirmation code should be send in the API response to use in the next API call.
Describe the issue:
In the user account recover API v2, WSO2 IS is sending the confirmation code and flow confirmation code appended with a dot.
With the improvement done in #14808, users can use an OTP instead of UUID in the recovery flows and utilize it in the API based implementation such as mobile applications that will utilize REST API to confirm.
When the flow confirmation code and the confirmation code are appended, it is not to show only the confirmation code without string manipulation.
It is required to send the confirmation code without appending the confirmation code to the user in the recovery flow.
How to reproduce:
Expected behavior:
Only the confirmation code should send in the email. Flow confirmation code should be send in the API response to use in the next API call.
Environment information:
[1] - https://is.docs.wso2.com/en/latest/apis/user-account-recovery-v2-rest-api/
The text was updated successfully, but these errors were encountered: