raphj opened a new issue, #1242:
URL: https://github.com/apache/directory-scimple/issues/1242
Instead of sending a `manager` field with a complex reference type with a
`$ref` and a `value` subfield, MS simply sends a `manager` field with the
`userName` as a string value.
They send something like:
```
{
....
"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User": {
...
"manager": "myuser"
}
}
```
instead of:
```
{
....
"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User": {
...
"manager": {
"$ref": "9fcafdba-f594-418f-8988-746fd0b449b3",
"value": "myuser"
}
}
}
```
See
https://learn.microsoft.com/en-us/answers/questions/188003/scim-user-provisioning-setup-with-manager-attribut.
This causes JSON validation to fail and the request is answered with a 500
error. This bug has been reported in 2020, they acknowledged the issue but
haven't fixed it.
At least, they do expect a compliant reply from the scim server...
We may want to work around this Entra ID quirk. It would be best for
Microsoft to fix their client, but I'm not quite sure we can count on this, and
I suppose the world has worked around MS's quirk by now as usual.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
