<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
0D51Y00009mOVPJSA4Okta Classic EngineIntegrationsAnswered2020-10-22T23:26:53.000Z2020-10-20T00:49:42.000Z2020-10-22T23:26:53.000Z

YixiaoT.60894 (Customer) asked a question.

Didn't get groups for specific user through okta-sdk-nodejs

Hi, our team are developing a service to get the users and groups info from the Okta API by okta-sdk-nodejs. We encountered a problem during the development. When we sent a request for one specific user through /api/v1/users/{{userId}}/groups API, the oktaClient.http.http() didn't reply until timeout. No error message threw and only happened on that user. After step-by-step debugging, we found that the https request returned successfully, and the problem occurred in the default cacheMiddlewar. setting cacheMiddleware to null in the oktacClient can fix this bug.

 

Although the bug is currently fixed, we hope to know the root reason of the bug. We guess the issue is related to response size. The user has more than 40 groups, maybe the oversized response caused this problem.


This question is closed.
Loading
Didn't get groups for specific user through okta-sdk-nodejs