[SLING-7937] A post to update a nested "Date" property for a user or group sets the property at the wrong path

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: JCR Jackrabbit User Manager 2.2.8
• Fix Version/s: JCR Jackrabbit User Manager 2.2.10
• Assignee: Eric Norman
• Reporter: Eric Norman
• Created: 18/Sep/18 22:22
• Updated: 04/Aug/20 18:21
• Resolved: 19/Sep/18 01:00

Description

When posting an update for a user or group, the handing of nested "Date" properties is not correct as it is setting the property at the wrong path.  It is ignoring the posted property path and setting the value using the property name as the path.  So post an update to "nested/key1" would store the value at "key1" instead of "nested/key1".

 

For example:

1. create a test user
   curl -u admin -F:name=user1 -Fpwd=password -FpwdConfirm=password http://localhost:8080/system/userManager/user.create.html
2. update a nested date property for the user
   curl -u user1 "-Fnested/key1=2018-10-10" "-Fnested/key1@TypeHint=Date" http://localhost:8080/system/userManager/user/user1.update.html
3. fetching the user resource json should not contain the "key1" value
   curl -u user1 http://localhost:8080/system/userManager/user/user1.json
4. instead it is expected that the "nested/key1" should be stored under the /home/users//[rep:User]/nested folder for the user
   curl -u user1 http://localhost:8080/user_path_from_json_from_#3_here/nested.json