There are four events:
- User update password for Okta
- User login to Okta
- Evaluation of Sign-on policy
- Verify user identity success
None of these events is unique to a user clicking on an activation link and activating their account.
I find it surprising and a little disappointing that there are dozens of obscure event types I can subscribe to, but yet one of the most important (and most obvious) events in the system - the point a which a user becomes ACTIVE - is not catered for. Seems a huge oversight?
For anyone else struggling with this:
I have a temporary workaround by listening for the User update password for Okta event. This
event is triggered whenever any user changes their password, so it’s not ideal, because my listener will get a lot of unnecessary invocations, but it can filter the events to find newly activating users by:
event.data.events.debugContext.debugData.requestUri === "/user/welcome/login/internal"
I’m not entirely sure this will cover all eventualities; for example, it won’t work if the user is imported with a pre-existing password and then activated or the user is activated through Inbound Federation. But it’s better than nothing.
I’d still strongly encourage anyone from Okta reading this to consider implementing a relevant event type. There are lots of Use Cases for Event Hooks when a user becomes fully active.