<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
0D54z0000A4pROrCQMOkta Classic EngineIntegrationsAnswered2024-05-31T17:02:59.000Z2024-05-14T10:29:53.000Z2024-05-31T17:02:59.000Z
Redundant /oauth2/default/v1/authorize calls, triggered by Okta

During consideration of https://developer.okta.com/docs/reference/rl-clientbased/ Okta's feature we noticed, that occasionally one of our applications, integrated with Okta triggers redundant "/oauth2/default/v1/authorize" calls, up to 8-10 with the following interval:

2024-03-04T16:35:46.740Z

2024-03-04T16:35:46.730Z

2024-03-04T16:35:46.733Z

2024-03-04T16:35:46.727Z

2024-03-04T16:35:46.783Z

2024-03-04T16:35:46.659Z

2024-03-04T16:35:46.730Z

We integrated using https://developer.okta.com/docs/guides/implement-grant-type/authcodepkce/main/*authorization-code-with-pkce-flow.

Meanwhile during troubleshooting, when authorizing and obtaining access and id token from within UI, our client applications trigger just appropriate calls & successfully obtain required tokens.

Can you please advice, what can be the cause of those redundant calls, triggered by okta libraries ?


This question is closed.
Loading
Redundant /oauth2/default/v1/authorize calls, triggered by Okta