Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[SCIM] can create a user with a corrupted email property

See original GitHub issue

Hello 😃

When creating a user without an email, then doing the following PATCH operations, the attributes in the DB do not have a value for parent_attribute_id.

To reproduce:

POST a user

{"schemas":["urn:ietf:params:scim:schemas:core:2.0:User","urn:ietf:params:scim:schemas:extension:enterprise:2.0:User"],"externalId":"78a07f0c-c4b9-47da-8cff-fd1fc5391dfc","userName":"test@test.com","active":true,"displayName":"Test Test","meta":{"resourceType":"User"},"name":{"formatted":"Test Test","familyName":"Test","givenName":"Test"}}

PATCH the created user

{"schemas":["urn:ietf:params:scim:api:messages:2.0:PatchOp"],"Operations":[{"op":"Add","path":"emails[type eq "work"].primary","value":"true"},{"op":"Add","path":"emails[type eq "work"].type","value":"work"}]}

Now theparent_attribute_id values will be null, and there won’t be an attribute with emails full path.

PATCH again

{"schemas":["urn:ietf:params:scim:api:messages:2.0:PatchOp"],"Operations":[{"op":"Add","path":"emails[type eq \"work\"].value","value":"test@test.com"},{"op":"Add","path":"emails[type eq "work"].primary","value":"true"},{"op":"Add","path":"emails[type eq "work"].type","value":"work"}]}

Now when you GET this user, you’ll see its email and other attributes as top level keys in the returned representation.

Do you know why is this happening?

Kind regards Dan