Skip to content

Packing SAML Response attribute values in an array when there is more than one xml node with the same key#112

Closed
miguelpais wants to merge 2 commits intoSAML-Toolkits:masterfrom
miguelpais:supporting-fetch-multiple-roles-from-saml-response
Closed

Packing SAML Response attribute values in an array when there is more than one xml node with the same key#112
miguelpais wants to merge 2 commits intoSAML-Toolkits:masterfrom
miguelpais:supporting-fetch-multiple-roles-from-saml-response

Conversation

@miguelpais
Copy link
Copy Markdown

Packing SAML Response attribute values in an array when there is more than one xml node with the same key.

This is useful, for instance, for fetching multiple roles assigned to a user, which currently is not supported (the last role defined will be the one retrieved because the key to value assignment on the attributes map keeps replacing the value).

… than one xml node with the same key (critical for fetching all the assigned roles to a user from the response)
@Lordnibbler
Copy link
Copy Markdown
Contributor

@miguelpais can you add specs for this?

@miguelpais
Copy link
Copy Markdown
Author

Done

@miguelpais
Copy link
Copy Markdown
Author

If you're wondering why I ended up doing this in the first place, it's because I happen to have some webapp using calh's fork of "ruby-saml" and integrating with Redhat's Picketlink solution, which happens to send user roles in this way on the SAML-response.

You can decide if this small functionality is useful or not.

P.S.: I happen to be using calh's fork and not the official ruby-saml, because, if I remember correctly, you guys didn't support the single logout scenario (by not allowing an sp from sending a logout-response).

@borgand
Copy link
Copy Markdown
Contributor

borgand commented Apr 1, 2014

I created a pull request #122 that fixes this issue in a backwards compatible manner

Lordnibbler pushed a commit that referenced this pull request Apr 1, 2014
Fixes #112 and #117 in a backwards compatible manner
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

Successfully merging this pull request may close these issues.

3 participants