<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
0D54z00009xRWgjCAGOkta Classic EngineIntegrationsAnswered2025-09-13T09:01:51.000Z2024-01-26T15:54:55.000Z2024-01-26T23:42:35.000Z

b0adp (b0adp) asked a question.

Variable results from get groups api calls with large filter

We are using the Okta API to pull user and group data into a third party application (Backstage). The api call is managed by a third party plugin. It allows us to filter groups, and due to needing only specific groups we are filtering by profile name: ie. profile.name eq “Team 1” or profile.name eq “Team 2” etc. We have 42 groups.

 

However, in our staging and production environments, we get a seemingly random number of groups each time we do the api request. It could be 20, or 36, or 25. We never seem to get the entire list of groups. Has anyone experienced an issue like this?

 

We don't have a good way to identify the groups other than by name, so we have a large filter of 'ors' and profile.name eq “Team 1” for each of the 42 teams. Is it possible that the large filter is causing issues?

 

It is also entirely possible this is not related to the api and some other issue we're having.

 

 

 


  • a0n5s (a0n5s)

    Do you use this api?

    https://developer.okta.com/docs/reference/api/groups/#list-groups-with-search

    it only told requires URL encoding 

    (opens new window)

    . For example, 

    search=type eq "OKTA_GROUP"

     is encoded as 

    search=type+eq+%22OKTA_GROUP%22

    . Use an ID lookup for records that you update to ensure your results contain the latest data. Search results are eventually consistent

     

    it not define the length limitation of the filter. The Url length for browse is very large.I think it is not length issue for browse.

     

    maybe you can test the length of filter, if short is working fine. I think you should create case with support team.

     

    it seems the filter expression is correct.

    https://developer.okta.com/docs/reference/core-okta-api/#pagination

     

    葛恒丰/Hengfeng Ge

     

    甫连信息/FreeLink

    电邮/E-Mail:  gehf@mfreelink.com

     

    Auth0 | BlackBerry | DocuSign | Netskope | Onfido | Okta | Sentinelone | Sumsub Varonis | Yubikey

     

    Expand Post
  • b0adp (b0adp)

    Yes, that is what is being used. We're not sure the problem lies with Okta. Really, we think it likely does not, but want to eliminate it for sure.

     

    API calls using the same exact one that our third party plugin uses consistently bring back the results we expect.

This question is closed.
Loading
Variable results from get groups api calls with large filter