New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In user retrieval JSON response has the type attribute malformed for certain multi-valued attributes #28

Closed
jgomer2001 opened this Issue Sep 12, 2017 · 1 comment

Comments

Projects
None yet
1 participant
@jgomer2001
Collaborator

jgomer2001 commented Sep 12, 2017

For the following multi-valued attrs: emails, phones, ims, address, the inner type subatribute is not being returned as

"type": "current_value"

but

"type":{ "value": "current_value" }

@jgomer2001 jgomer2001 added this to the CE 3.2 milestone Sep 12, 2017

@jgomer2001 jgomer2001 self-assigned this Sep 12, 2017

@jgomer2001 jgomer2001 added the bug label Sep 12, 2017

@jgomer2001

This comment has been minimized.

Collaborator

jgomer2001 commented Sep 27, 2017

Newer custom serialization mechanism prevents this to happen https://github.com/GluuFederation/oxTrust/blob/scim2_compliance/server/src/main/java/org/gluu/oxtrust/ws/rs/scim2/BaseScimWebService.java#L182-L182.

Serialization routine traverses the SCIM resource as a tree and thus generated json content reflects the structure of original resource. In traversal, the exclussion or inclussion of attributes in response is applied.

This applies to any operation (CRU). It solves #27

@jgomer2001 jgomer2001 closed this Sep 27, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment