<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
0D54z000073DDiVCAWOkta Classic EngineIntegrationsAnswered2024-03-25T06:28:44.000Z2021-07-05T22:38:46.000Z2021-07-09T06:45:40.000Z

wyboa (wyboa) asked a question.

https://xxx-partners.okta.com/oauth2/some_id/v1/token took too long

We use https://xxx-partners.okta.com/oauth2/some_id/v1/token before querying GraphQl. Sometimes it took too long to refresh the token (7 cases among 8,548 API calls, from 1.39s to 2.33s). Our client requires 1.5s for latency therefore these gave us hard time to satisfy our users. Any suggestion to handle these long auth token refresh?


  • Hi Yingdan,

     

    This needs proper investigation to see exactly what was the max response time from our servers on a specified time frame. As we don`t have any details about the organization we cannot move forward with providing a resolution.

    Please do open a case with us to further investigate.

    Expand Post
This question is closed.
Loading
https://xxx-partners.okta.com/oauth2/some_id/v1/token took too long