Hello SCIMple community,
I'm writing regarding the 1.0.0-M2 release that was tagged on GitHub (Feb 19,
2025) but doesn't appear to be available on Maven Central yet.
Background: We're migrating from an internal SCIMple fork to the official
release. However, 1.0.0-M1 (currently the only version on Maven Central) has an
issue with PATCH operations on complex attributes that's blocking our migration.
The Issue in M1: Multiple PATCH replace operations without explicit paths
targeting different sub-attributes of a complex attribute don't merge correctly:
PATCH /Users/{id}
{
"schemas": ["urn:ietf:params:scim:api:messages:2.0:PatchOp"],
"Operations": [
{
"op": "replace",
"value": {"name": {"familyName": "UPDATED_FAMILY"}}
},
{
"op": "replace",
"value": {"name": {"givenName": "UPDATED_GIVEN"}}
}
]
}
In M1, only givenName is set; familyName becomes null.
The Good News: This was fixed in commit 656762e (Jan 22, 2025), and I've
confirmed this fix is included in the v1.0.0-M2 tag on GitHub.
Question: What's the timeline for publishing 1.0.0-M2 to Maven Central? Our
comprehensive test suite includes coverage for this PATCH scenario, so we
cannot complete our migration until M2 is available.
We're eager to move forward and I would be happy to help with testing if needed.
Thanks for maintaining this project!
Best regards,
Josh Steele
Joshua Steele
Software Engineer III
Mobile: +1.419.705.6336
[cid:[email protected]]<https://www.proofpoint.com/>
