No it is doing one call POST /Users for creating a user , below is how my setting looks like in the application xml file
<key=“skipGrpUpdate” value=“true”/>
<key=“updateGroupsViaUsers” value=“true”/>
If I make <key=“skipGrpUpdate” value=“false”/> it is making two calls 1) POST /users with null value in groups and 2) PUT /Users call with add entitlement.
but this is not we expected, we want the POST /Users call itself should be sending the entitlements along with POST call but it is coming as null in out case.
With the above settings, if it is not a new user it will calling the patch right ?
If so we don’t have patch API
we just have PUT for both /Users and /Groups
we just have PUT and POST no PATCH
even if I use this option in debug page as you suggested key=“skipGrpUpdate” value=“false” and usePatch is true
, we are getting group as null
{"id":null,"schemas":["urn:ietf:params:scim:schemas:core:2.0:User"],"userName":"aaaaa","groups":null,"active":true,"meta":null}"