...
Solution 1 - Add isBlocked field in User DynamoDB item
Workflow:
Support agent blocks the user
Zenuml sequence macro lite |
---|
uuid | b71e9351-b423-4ec1-ba13-9349ce24c6aa |
---|
customContentId | 4810997767 |
---|
updatedAt | 2024-06-19T01:56:16Z |
---|
|
|
Blocked user attempts login
Zenuml sequence macro lite |
---|
uuid | 9e561ae4-39d8-4c19-81ba-99e914394741 |
---|
customContentId | 4810997776 |
---|
updatedAt | 2024-06-19T02:01:46Z |
---|
|
|
User is blocked while logged in WL
Zenuml sequence macro lite |
---|
uuid | 5495a0ee-0cbb-4042-8755-8a716fa406f1 |
---|
customContentId | 4810965031 |
---|
updatedAt | 2024-06-19T02:08:58Z |
---|
|
|
Task breakdown
Changes in intl-notifications-service
Changes in intl-users-service
Create block user endpoint
Expand |
---|
|
Endpoint: POST /api/v1/users/block-user/{cognitoId} Add isBlocked field to user details base interface Use UpdateService to set is blocked to true
|
Create unblock user endpoint
Prevent blocked users from signing in
Expand |
---|
|
Create UserBlockedError apollo error (ex:) Add isBlocked validation in the listed resolvers: createOTP createLoginOTP signInJWT socialLogin
User not found validation for reference
|
Changes in intl-whitelable-graphql
Add isBlocked to userDetails type
Changes in intl-whitelable-app
Solution 2 - Disable user in cognito