[
https://issues.apache.org/jira/browse/KNOX-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16191076#comment-16191076
]
ASF subversion and git services commented on KNOX-1069:
-------------------------------------------------------
Commit 5de920bd092d2822a32aa546d01bb8e64de3a5a9 in knox's branch
refs/heads/master from [~coheigea]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=5de920b ]
KNOX-1069 - KnoxSSO token audience config should trim values
> KnoxSSO token audience config should trim values
> ------------------------------------------------
>
> Key: KNOX-1069
> URL: https://issues.apache.org/jira/browse/KNOX-1069
> Project: Apache Knox
> Issue Type: Improvement
> Components: KnoxSSO
> Affects Versions: 0.13.0
> Reporter: Jeff Storck
> Assignee: Colm O hEigeartaigh
> Priority: Minor
> Fix For: 0.14.0
>
>
> knoxsso.token.audiences can be set to a comma-separated list of values.
> Those values can end up containing spaces, depending on how the list is
> configured. For example:
> {code:xml}
> <param>
> <name>knoxsso.token.audiences</name>
> <value>foo,bar, baz</value>
> </param>
> {code}
> With that config, the token seen by the receiving service will see three
> audiences, "foo", "bar", and " baz". Notice the space in front of baz.
> If the list is parsed and the values are trimmed, it might avoid confusion
> for services that need to parse that list and match values. Other areas
> within Knox (such as federation filters) should also trim the values in the
> list for matching purposes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
