I am facing the next issue. Our company has SCIM service which worked perfectly with Azure `EntraID`. Currently, we are trying to reuse it with Okta provisioning. Users synchronization works correct and users are added to our system successfully. While trying to provision Groups we faced the next issue:

New Group `Custom_Developers` was created with single test user. This test user is already assigned to Application and successfully provisioned.

New Group Push is created to synchronize Groups details with our system. 'Create Group' option is selected as no Group was previously created.

After saving all changes and applying group push new Group is created in our system with correct name 'Custom_Developers', but member array is empty, so no user is linked to this group.

From our logs, I can clearly see that POST api/scim/v2/Groups endpoint is triggered.

After that, we tried to push group again with same members but from our logs only GET api/scim/v2/Groups/684f9f69-5113-4566-81c2-7afd201e19f6 is triggered where 684f9f69-5113-4566-81c2-7afd201e19f6 is the correct Id of Custom_Developers group from our system.

In Okta, there is error message 'Unable to update Group Push mapping target App group <GroupName>: Error while creating user group <GroupName>: Not Found'

I am wondering, if Okta is trying to create group again? After running the same endpoint using Postman the response is

{

    "meta": {

        "resourceType": "Group",

        "created": "0001-01-01T00:00:00",

        "lastModified": "0001-01-01T00:00:00",

        "version": null,

        "location": null

    },

    "displayName": "Custom_Developers",

    "members": [],

    "id": "684f9f69-5113-4566-81c2-7afd201e19f6",

    "schemas": [

        "urn:ietf:params:scim:schemas:core:2.0:Group"

    ]

}

This response looks correct, but does it miss something for the correct work?