...
Changes in intl-admin-app
Expand |
---|
|
Create block status card on customer page Update users package Add isBlocked to user details type in graphql Add isBlocked to customer query in frontend Create card to display user status
Create mutation to block the user Use blockUser exposed in the user package (instantiated insider the user provider) Create auditLog for the customer blocking Create new audit action block-user Example of audit log
Check if the agent has permission to block TBD: which permission is needed
Implement block user in front end Create confirmation modal Check if agent has permission to change customer status TBD: which permission is needed
Trigger block mutation on confirmation
Create mutation to unblock the user Use unblockUser exposed in the user package (instantiated insider the user provider) Create auditLog for the customer unblocking Create new audit action unblock-user Example of audit log
Check if the agent has permission to unblock TBD: which permission is needed
Implement unblock user in front end Create confirmation modal Check if agent has permission to change customer status TBD: which permission is needed
Trigger unblock mutation on confirmation
|
Changes in intl-whitelable-app
Expand |
---|
|
Create blocked account modal Handle UserBlockedError in signIn Option 1 Create onError handler for signIn mutations If UserBlockedError: sign out user display blocked account modal
Add onError parameter to the following signIn mutations signInWithOtp signInWithJwt signInSocialLogin
Option 2 Monitor error value of all the mutations listed above with useEffect If UserBlockedError: sign out user display blocked account modal
Validate if user is blocked before proceeding to cart use getMe query to check user status if isBlocked sign out user display blocked account modal
|
Solution 2 - Disable user in cognito