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

editing attribute has unacceptable value for "multivalued" by default #1060

willow9886 opened this Issue Aug 2, 2018 · 2 comments


None yet
5 participants

willow9886 commented Aug 2, 2018


Trying to edit an attribute in oxTrust, password, but for some reason the default value for multivalued field is multivalued which is an unacceptable value for that field.

This seems to be the case for editing any attribute. They all have default value for multivalued to multivalued even though thats not an acceptable value..

So basically to edit any attribute, you also have to set an acceptable value for multivalued. Shouldn't the field be set to an acceptable value by default??

@willow9886 willow9886 added this to the 3.1.4 milestone Aug 2, 2018

@syntrydy syntrydy self-assigned this Aug 3, 2018

syntrydy pushed a commit that referenced this issue Aug 3, 2018

yurem added a commit that referenced this issue Aug 8, 2018

Merge pull request #1065 from /issues/1060
Fix multivalue field issue #1060

@syntrydy syntrydy closed this Aug 12, 2018


This comment has been minimized.

natt-tester commented Sep 6, 2018

@syntrydy, I think we still need improvement in this issue: I've checked two random Attributes and they are not set to their default values as @willow9886 suggested; the "Multivalued" string is just cleared from the first dropdown option:


@natt-tester natt-tester reopened this Sep 6, 2018


This comment has been minimized.


syntrydy commented Sep 6, 2018

@natt-tester that is the expected behavior.

From the UI point of view, you can add an attribute with multivalued set to null, however Gluu ship with multiples attributes with that field set to null. These are attributes added via scripts and installation time, so no mean to enforce the field value.

So it is okay as it is right now.

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