<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D5KZ00000hTZP80AOOkta Identity EngineAdministrationAnswered2025-04-18T22:36:35.000Z2025-04-18T22:06:19.000Z2025-04-18T22:36:35.000Z

EricL.78638 (Customer) asked a question.

Why is our inline password hook sometime called with Okta System (SystemPrincipal)?

We have used an inline password hook since August last year successfully. We think our users are mostly migrated by now and we want to check who is still calling us. Using the Admin console, System Log filtering by `eventType eq "inline_hook.executed"` we are seeing calls where the Actor is `Okta System (SystemPrincipal)` while others, the Actor is the user actually invoking the hook.

Why the difference? All our users use the same web application to authenticate

/help/servlet/rtaImage?refid=0EMKZ000000FkGo


  • DianaL.19788 (Customer Support Online Community and Social Care)

    Hello @EricL.78638 (Customer)​ , thank you for contacting Okta Community!

    I've reviewed our documentation for something relevant. It looks like your question is more appropriate for our dedicated Okta Developer Forum. I advise reaching out via devforum.okta.com  as they will have more insight into this topic. 

    In the meantime, you can reference this general guide from Okta Developer: 

    Inline Hooks

     

    While we'll do our best to answer your questions here, this medium is more inclined towards Okta's core products and features (non-developer work).

     

    Regards. 

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Collect them all. Learn a new skill and earn a new Okta Learning badge.

    Expand Post
This question is closed.
Loading
Why is our inline password hook sometime called with Okta System (SystemPrincipal)?