[
https://issues.apache.org/jira/browse/KNOX-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15210347#comment-15210347
]
ASF subversion and git services commented on KNOX-697:
------------------------------------------------------
Commit 61b4f8d2418e7b459aa74f57d074afbf1382c277 in knox's branch
refs/heads/master from [~kevin.minder]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=61b4f8d ]
[KNOX-697] - Identity asserter provider that supports case mapping for users
and groups
> Identity asserter provider that supports case mapping for users and groups
> --------------------------------------------------------------------------
>
> Key: KNOX-697
> URL: https://issues.apache.org/jira/browse/KNOX-697
> Project: Apache Knox
> Issue Type: New Feature
> Components: Server
> Affects Versions: 0.9.0
> Reporter: Kevin Minder
> Assignee: Kevin Minder
> Fix For: Future
>
> Attachments: KNOX-697_001.patch
>
>
> There have been numerous occasions where downstream ecosystem components have
> required user and group names to be specific case. Currently Knox does not
> enforce the case of the user or group identity and will use whatever is
> accepted by the authentication provider. The request here is to add a new
> identity-assertion provider that could be configured to do case mapping on
> user and group names. It might be configured in a topology file something
> like what is shown below.
> {code:xml}
> <provider>
> <role>identity-assertion</role>
> <name>SwitchCase</name>
> <param name="user" value="upper"/>
> <param name="group" value="upper"/>
> <enabled>true</enabled>
> </provider>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
