Current Limitation

Currently, the HTML page displayed after successful self-registration does not have access to the newly created user's userId. This poses a challenge for integration with external vendors who require the userId to manage user data and comply with data residency regulations.

Use Case:

• Consider a scenario where an external vendor provides data residency solutions. This vendor acts as a proxy, keeping certain user personal information within their system while allowing Asgardeo to store only masked or anonymized user data. To link the user data stored by the vendor with the user record in Asgardeo, the vendor needs access to the userId immediately after the user registers.

Problem

• Without the userId being available on the front-end, the external vendor cannot establish this link, hindering their ability to provide data residency services and comply with relevant regulations.

Suggested Improvement

Enhance the self-registration API[1] to include the userId in its response, and update the self registration processing and completion related JSP pages to extract and store this userId in a hidden input field.

[1] https://is.docs.wso2.com/en/latest/apis/use-the-self-sign-up-rest-apis/#tag/Self-Register

Version

No response