2549y (2549y) asked a question.
Okta is integrated with another customized component which supports SCIM requests and performs certain steps. Unassigning a user from the Application does not throw an error if any.
Flow to reproduce - Choose an application. Unassign any user from the list. Set up a condition where unassigning a user would fail.
Once the unassign button is clicked, the user gets unassigned from the list on the Okta, but if there are any errors to perform the follow up steps they are not showed up on the screen. A message "User has been unassigned" shows up, but on the backend the next steps are not performed since there is an error. So the flow is not complete with no error message.
This also happens when assigning the user was not successful(image 1) and has a red exclamatory mark, but unassigning the user shows a success message(image 2). Is this behavior expected? if yes, how to notify the user/admin of the account that there was an error?
The unassignment doesn't show on the application page. The unassignment usually also removes the user from SSO access, so access is effectively blocked.
The SCIM provisioning error will be shown on Dashboard -Tasks. You can also run a workflow to poll the audit logs for failures and notify a service/helpdesk/admin.
But really, fix the SCIM endpoint and remove the errors.
Thank you for the information on how to view errors and clarifying the behavior!