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
When the user sign-up workflow is enabled and a user self-signs up, the request is sent to the Admin Portal for approval. However, if the user is deleted from the Carbon Console or via an Admin Service without rejecting the request, the user request remains in the Admin Portal. Additionally, if the same user self-signs up again, the new request is processed, but the previous user request still persists in the Admin Portal, leading to duplicate entries.
Steps to Reproduce
Scenario 1
Start the wso2 api manager server.
Login to the carbon console and enable self-signup workflow. [1]
Navigate to the Devportal and self sign-up a user.
The user request is sent to the Admin Portal for the approval.
Now delete the user from the Carbon Console.
Login to Admin Portal and navigate to the User Cration tab.
Expected: Particular user request to be deleted. Actual: The user request exists in the Admin Portal.
Scenario 2
Start the wso2 api manager server.
Login to the carbon console and enable self-signup workflow. [1]
Navigate to the Devportal and self sign-up a user -> (user: isuruuy)
The user request is sent to the Admin Portal for approval.
Expected: Particular user request to be deleted. Actual: It gets a 200 successful response for the Admin Service request, but the user request exists in the Admin Portal.
Description
When the user sign-up workflow is enabled and a user self-signs up, the request is sent to the Admin Portal for approval. However, if the user is deleted from the Carbon Console or via an Admin Service without rejecting the request, the user request remains in the Admin Portal. Additionally, if the same user self-signs up again, the new request is processed, but the previous user request still persists in the Admin Portal, leading to duplicate entries.
Steps to Reproduce
Scenario 1
Expected: Particular user request to be deleted.
Actual: The user request exists in the Admin Portal.
Scenario 2
Expected: Particular user request to be deleted.
Actual: It gets a 200 successful response for the Admin Service request, but the user request exists in the Admin Portal.
[1] - https://apim.docs.wso2.com/en/latest/reference/customize-product/customizations/adding-a-user-signup-workflow/
Version
4.3.0.38
Environment Details (with versions)
user sign-up workflow enabled.
wso2am-4.3.0.38
MacOS Sonoma 14.4
The text was updated successfully, but these errors were encountered: