I created the JIRA and the pull request linked to it. This solves my
problem. All the existing integration tests continue passing. I don't know
if I need to write any more special integration tests for this case.
On Fri, Sep 30, 2016 at 10:06 AM Stian Thorgersen <sthorger(a)redhat.com>
Looks like a limitation of the user attribute importer:
It simply picks the first value and uses that.
You can create a JIRA feature request to have support for importing multi
valued attributes. A PR for this would be great if you're up for it. If you
need a solution quick you can create your own custom mapper.
On 28 September 2016 at 11:04, Manuel Palacio <emanuel.palacio(a)gmail.com>
I am trying to process a SAML attribute with multiple values.
To that end I have created a client mapper of type User Attribute with
I also have an "attribute importer" mapper in the SAML v2.0 identity
provider. It points to user attribute name defined in the client mapper
Unfortunately, it is only mapping the first value into the access token.
The attribute in the SAML response looks like this
value1</AttributeValue> <AttributeValue>value2</AttributeValue> <
In the access token only the first value appears as part of "otherClaims"
What do I need to do in order to get all the values in the access token?
keycloak-user mailing list