Closed NekoLuka closed 9 months ago
Describe the bug When making use of the advanced tool, the groups are created with a value that does not follow the SCIM standard as described in RFC 7643. Looking like this:
{ "schemas":[ "urn:ietf:params:scim:api:messages:2.0:PatchOp" ], "Operations":[ { "op":"Add", "path":"members", "value":[ { "value":"7aee3963-496d-43e8-a069-e0a2d880d20f" } ] } ] }
To Reproduce Steps to reproduce the behavior:
Expected behavior I would expect it to follow the description as stated in RFC 7643 section 4.2. See example below:
{ "schemas":[ "urn:ietf:params:scim:api:messages:2.0:PatchOp" ], "Operations":[ { "op":"Add", "path":"members", "value":[ { "id":"7aee3963-496d-43e8-a069-e0a2d880d20f" "$ref":"https://myservice.com/Users/7aee3963-496d-43e8-a069-e0a2d880d20f" } ] } ] }
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context Add any other context about the problem here.
Nevermind, I see that I read the spec wrong.
Describe the bug When making use of the advanced tool, the groups are created with a value that does not follow the SCIM standard as described in RFC 7643. Looking like this:
To Reproduce Steps to reproduce the behavior:
Expected behavior I would expect it to follow the description as stated in RFC 7643 section 4.2. See example below:
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context Add any other context about the problem here.