Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[User Signup Workflow enabled] Once a user is deleted from the Carbon Console, user request is not deleted from the Admin portal. #3513

Open
isuruuy429 opened this issue Jan 10, 2025 · 0 comments

Comments

@isuruuy429
Copy link

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

  1. Start the wso2 api manager server.
  2. Login to the carbon console and enable self-signup workflow. [1]
  3. Navigate to the Devportal and self sign-up a user.
  4. The user request is sent to the Admin Portal for the approval.
  5. Now delete the user from the Carbon Console.
  6. 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

  1. Start the wso2 api manager server.
  2. Login to the carbon console and enable self-signup workflow. [1]
  3. Navigate to the Devportal and self sign-up a user -> (user: isuruuy)
  4. The user request is sent to the Admin Portal for approval.
  5. Delete the user from the following Admin Service.
curl --location 'https://localhost:9443/services/UserAdmin.UserAdminHttpsSoap11Endpoint' \
--header 'Content-Type: text/xml' \
--header 'SOAPAction: urn:deleteUser' \
--header 'Authorization: Basic YWRtaW46YWRtaW4=' \
--header 'Cookie: JSESSIONID=1B53B5F72FD05DA303B0CEA70EF6E2AC; requestedURI=go-back-uri/go-back-uri/fhir/r4/metadata' \
--data '<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://org.apache.axis2/xsd">
   <soapenv:Header/>
   <soapenv:Body>
      <xsd:deleteUser>
         <!--Optional:-->
         <xsd:userName>isuruuy</xsd:userName>
      </xsd:deleteUser>
   </soapenv:Body>
</soapenv:Envelope>'

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant