<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
0D51Y00006IlhJHSAZOkta Classic EngineAdministrationAnswered2025-06-29T09:00:41.000Z2019-05-31T15:30:31.000Z2020-04-06T12:56:38.000Z

fishere.26559 (Customer) asked a question.

Okta Rest API HTTP Connection/Socket Timeouts

Note: I don't think there was an appropriate category for this question...

 

We're running into issues with our Java Apache HttpClient ConnectManager using stale connections when attempting to execute Http Requests against the Okta Admin APIs. It looks like Okta is not terminating idle connections gracefully.

 

I looked all over but could not find any supporting documentation around this:

 

What are the recommended Http Connection timeout configurations when interacting with the Okta Rest APIs?


  • Hi Fisher,

    The global timeouts @Okta are Connect timeout (MS) 60000 / Read timeout (MS) 60000 and these are the recommended timeout configuration when interacting with Okta API. Thank you,

    Selected as Best
  • Hi fisher - thanks for taking time time to look for supporting documentation around this! I've escalated your question to our support team who should be able to help you out.

  • Hi Fisher,

    The global timeouts @Okta are Connect timeout (MS) 60000 / Read timeout (MS) 60000 and these are the recommended timeout configuration when interacting with Okta API. Thank you,

    Selected as Best
  • nmz8a (nmz8a)

    Hi, any possibility to change that. User will not wait 60 seconds when click log me in, or create account buttons.

    Thanks

This question is closed.
Loading
Okta Rest API HTTP Connection/Socket Timeouts