handle SCIM schema extensions on patch_update #28
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why?
When the
ScimUsersController#patch_updateendpoint was hit and had anoperationwith apathvalue that used SCIM's schema extensionsurn:ietf:params:scim:schemas:extension:enterprise:2.0:User, it would not parse this parameter properly resulting in the underlying attribute never getting updated.What?
Added a handler for scenarios where we receive a paramater that is part of SCIM's schema extensions. It isn't pretty but it gets the job done.
Also refactored a case statement that didn't handle when the operation sent the
activeattribute as"True"or"False". Simplified it to cast it as a boolean to handle that scenario and get rid of the case statement