Resolution Steps:

1. Verify API Version:
   • Ensure you are using API 2.1 for user deletion operations.
   • Update any /api/2.0/ endpoints to /api/2.1/ or GraphQL.
2. Use GraphQL Mutation for User Deletion:
   • Implement the CloseUserAccount mutation for user deletion.
   • Ensure the API user has the necessary permissions and authentication.
3. GraphQL Mutation Example (JSON format):

   {
     "query": "mutation CloseUserAccount($id: ID!, $password: String) { closeUserAccount(id: $id, password: $password) { result errors { ... on Error { __typename message } } } }",
     "variables": {
       "id": "user:<USER_ID_TO_BE_REMOVED>",
       "password": "<PASSWORD_OF_THE_ACCOUNT_AUTHENTICATED_VIA_OAUTH>"
     },
     "operationName": "CloseUserAccount"
   }
   
   

   • Replace <USER_ID_TO_BE_REMOVED> with the numerical user ID.
   • Replace <PASSWORD_OF_THE_ACCOUNT_AUTHENTICATED_VIA_OAUTH> with the actual password for the user authenticated via oAuth.
4. GraphQL Mutation Example (GraphQL format):
   

   mutation CloseUserAccount($id: ID!, $password: String) {
     closeUserAccount(id: $id, password: $password) {
       result
       errors {
         ... on Error {
           __typename
           message
         }
       }
     }
   }

   • Replace <USER_ID_TO_BE_REMOVED> with the numerical user ID.
   • Replace <PASSWORD_OF_THE_ACCOUNT_AUTHENTICATED_VIA_OAUTH> with the actual password for the user authenticated via oAuth.
5. Verify Resolution:  
   • Execute the mutation in Postman or a similar tool.
   • Confirm the result is true; if not, check for errors in the response.
     

Important: Ensure your authentication method is compatible with API 2.1 and that the API user has the correct permissions for user deletion in Aurora.