Skip to content
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

Address not compliant with RFC7643 #180

Open
wwebers opened this issue Jan 16, 2019 · 2 comments
Open

Address not compliant with RFC7643 #180

wwebers opened this issue Jan 16, 2019 · 2 comments

Comments

@wwebers
Copy link

wwebers commented Jan 16, 2019

Description:
The address object not compliant with RFC7643 section 4.1.2 where it is defined as a multivalued complex datatype.

The current release (and probably even older ones) realizes Address just as complex datatype. As such the other mandatory attributes such as value or display are omitted.

Affected Product Version:
Current carbon release.

OS, DB, other environment details and versions:
All OS
Steps to reproduce:
Take a look at https://tools.ietf.org/html/rfc7643#section-4.1.2

@jrussellsmyth
Copy link

This is incorrect. The "addresses" attribute is multivalued, consisting of address complex objects.

addresses is defined as a multivalue object here
https://github.com/wso2/charon/blob/master/modules/charon-core/src/main/java/org/wso2/charon3/core/schema/SCIMSchemaDefinitions.java#L801-L811

  • the fourth parmeter of createSCIMAttributeSchema is a boolean for "isMultivalue"

@wwebers
Copy link
Author

wwebers commented Oct 31, 2024

Will have to check that again. However, I wrote the issue for 6 years ago and haven't followed the development since about 5 years as I never got any reply.
So, maybe this isn't an issue anymore, I don't know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants