-
-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SCIM POST /Users with "manager.value" throws error 500 #714
Comments
Hello, To assist you in migrating from version 2.0.25 to 4.7, we have summarized the different steps:
Could you try migrating to version 4.0.7? We are considering migrating the entire SimpleIdServers solution to DOTNET8.0 soon, after the release of 4.0.8 :) |
Hello, thanks a lot for the migration help!
The So far I was able to test the "manager.value" issue and it seems to work in the latest v4.0.7 of SCIM, but then I got other 500 errors in other requests like PATCH and PUT /Users and POST /Bulk that I'm trying to find more details on. |
Since the error in the title and description seems solved in the latest v4.0.7, and the remaining stuff is something else, |
In the "SimpleIdServer.Scim" package library, if an enterprise user is created using:
POST /Users
with amanager.value
having the value of another user's SCIM Id (as per the RFC), then SCIM library throws a 500 error with the message:"Sequence contains no matching element"
.Also strangely it allows me to set any string in "manager.value" as far as it is not a userId, not sure if it should be validated or not, but it at least should work when the value is a correct userId.
How to reproduce this bug
Here is an example, first creating the user1 that will be the manager:
POST /Users
Returns 201 Created:
then creating the user2 that will have user1 as manager:
POST /Users
Results in error 500:
"Sequence contains no matching element"
.This was working fine in v2.0.25 where it wasn't throwing exception but returning 201 Created.
We discovered this issue while upgrading to v4.0.3.
Couldn't test the currently latest v4.0.7 because that version breaks even more things and couldn't get past all the other errors to test this issue.
The text was updated successfully, but these errors were encountered: