Closed CypagoTest closed 9 months ago
@monde @bogdanprodan-okta @duytiennguyen-okta @emanor-okta @bretterer Guys , can you please investigate this issue? it cost us a lot.
BR, Cypago
There is a bug in the Okta API on the groups endpoint where pagination appears to be broken. I'm running it down internally at Okta with the responsible feature team. okta-sdk-golang is down stream of the API.
Okta internal reference: OKTA-633507
This bug is only exhibited if the last group when paginating is the Admin Group. I don't believe everyone would necessarily experience this bug.
This issue has been marked stale because there has been no activity within the last 14 days. To keep this issue active, remove the stale
label.
This issue has been marked stale because there has been no activity within the last 14 days. To keep this issue active, remove the stale
label.
Okta will be deploying the fix for this issue into production on October 10th Okta internal reference: https://oktainc.atlassian.net/browse/OKTA-633507
@monde is this issue fixed, can we collect the groups with the pagination without any problems?
Yes that should be fixed
Describe the bug?
im using Golang Okta SDK , im collecting users, roles, apps, and groups from okta. all API endpoints looks good, but Group.ListGroups endpoint is not working with pagination. once i get all groups from Okta, resp.HasNextPage() return me not nil value, and i got infinitive loop and as a result run time error.
What is expected to happen?
Once i received all groups from Okta, i want to get resp.HasNextPage() false, and break the collection.
What is the actual behavior?
for loop collection stacked with run time error, as resp.HasNextPage() return true every time, even if we do not more groups to collect.
Reproduction Steps?
Additional Information?
No response
Golang Version
go version go1.20.3 darwin/arm64
SDK Version
github.com/okta/okta-sdk-golang/v2/okta
OS version
Mac , but for Linux the same.