<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
0D51Y00008vcuf3SAAOkta Classic EngineAdministrationAnswered2024-04-15T11:18:53.000Z2020-07-09T16:17:09.000Z2020-07-23T23:41:09.000Z

t2fjg (t2fjg) asked a question.

Token in-line hooks and Default Authorization server

Hello okta community,

I have a question about token in-line hooks. The documentation about token Inline hook (https://developer.okta.com/docs/reference/token-hook/) says that the hook only works with a custom authorization server and not the default server. "This Inline Hook works only when using an Okta Custom Authorization Server, not the built-in Okta Authorization Server." But I read the working example posted on okta developer blogs (https://developer.okta.com/blog/2019/12/23/extend-oidc-okta-token-hooks) using default auth server and was able to successfully do a small POC. The token inline hook worked like a charm by adding custom claims to the tokens minted by the default auth server. We are planning on taking this approach to production environment.

So, my question is, why does the documentation says that the hooks will work only with custom auth servers. Are there any gotchas that I am missing? Can somebody please confirm that this approach works without any issues?

Thanks in advance.


This question is closed.
Loading
Token in-line hooks and Default Authorization server