I want to add approval/rejection to the Okta registration or app assignment flow. The diagram below looks promising except that it looks like the hook is a synchronous call and won’t work for a long running manual process like manual approval/rejection. Any suggestions how to handle this scenario?
I have the exact same requirements which I took on today. I will keep you posted if I find a solution. Please let me know if you find the solution early.
We end up using the Okta event hook, based on the type of event, you can enable the trigger to your external web-service where you can control the approval/rejection.
The detailed process would looks something like-
While user registers, add him/her to temp group and add a low access sign on policy to control the access.
Register event hook and enable it for event like “user activation” or “user to group membership” etc.
Note: You would need your webservice to be ready for step 2.
Once you receive event payload, you can initiate the business approval workflow.
If approved, make an api call to remove the user from group else remove user from Okta
Thanks for sharing your solution This would work. We could then for instance trigger business approval workflow on “user create” or an “import inline hook”. When the manager approves/rejects user we could then call Okta API to “activate user”
or “remove user”.