To reproduce:
- Create a user and add some custom profile attribute, in my case the attribute is a string named "uuid"
- POST to /api/v1/users/:id following the example given here https://developer.okta.com/docs/api/resources/users.html#update-user
- See that the custom profile attribute has been cleared out/set to null
I created an issue in the stormpath-sdk-java repository thinking that the implementation of that SDK had a bug, but after circumventing that SDK entirely to make Okta API calls, I am still getting this behavior.
Our user profiles include a uuid that is important for our current authorization system. Currently all attempts to reset a password clears out all custom properties from our user profiles. POST vs PUT does not make a difference, the uuid is always cleared out of the profile.
This is how I'm performing the update: okta_user_update.txt
To reproduce:
I created an issue in the stormpath-sdk-java repository thinking that the implementation of that SDK had a bug, but after circumventing that SDK entirely to make Okta API calls, I am still getting this behavior.
Our user profiles include a uuid that is important for our current authorization system. Currently all attempts to reset a password clears out all custom properties from our user profiles. POST vs PUT does not make a difference, the uuid is always cleared out of the profile.
This is how I'm performing the update: okta_user_update.txt