According to documentation, Okta group names are unique. We’ve found that this enforced when adding groups through the Okta Admin UI, and also when we manually create groups via the Groups API (e.g. via Postman or whatnot).
However, we have an application which uses the Okta API to create groups. In our lower (non-prod) environments, this application communicates with an Okta Preview org. We run nightly automation tests against the application which results in multiple calls to create Groups in Okta, with auto-generated names.
We’ve begun getting error responses indicating that our Create Group calls are failing because a group with the same name already exists. When we went and looked at our groups in the Okta Admin UI we found the group name in question WAS already in use. But it was in use for multiple groups. In some cases, up to 4 groups had the same identical name (and we verified that there were no leading/trailing/internal whitespace differences).
We’re working to reproduce the issue. But wanted to reach out and see whether folks had any idea how we could have managed to create groups with duplicate names. Up until recently, we’d also been employing Workflows to create groups, so we thought perhaps there was some conflict between those workflows and our API calls. But since Workflows, in the end, simply call the API themselves, we couldn’t come up with any reasonable way that would be the culprit.
So my question is has the issue of creating duplicate groups been raised before?
Any ideas what we could be doing to cause it?
Attached image is an example from the Groups page showing two groups with identical names.
(The long wonky names are due in part to the fact that they’re auto-generated by automation tests.)