[
https://issues.apache.org/jira/browse/CONNECTORS-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13689071#comment-13689071
]
Maciej Lizewski commented on CONNECTORS-703:
--------------------------------------------
I was thinking about plugin with UI just like you described... but if there is
another option - maybe we could go different way.
As for the use case - I think that with growing set of auth connectors we will
need such functionality for sure to deal with configurations using multiple
different auth connectors. There are companies without single authorization
service which use security models from different systems (like shared folders,
Jira, web, etc) where the only way to unify user accounts is to provide
sophisticated mapper... In such configurations you have to choose one
authentication center to authenticate user and get its ID passed to getUserACLs
servlet, but then user ids can be different in other auth centers and for
example they can only be mapped one to another by users e-mail which is just
profile attribute, not the main user ID. We are talking with such client right
now about deploying internal indexing/search engine and we will need to write
wrappers for current auth connectors to do the mapping.
Anyway - we can postpone this functionality, and for now we will go with
wrappers :)
> add username mappers functionality
> ----------------------------------
>
> Key: CONNECTORS-703
> URL: https://issues.apache.org/jira/browse/CONNECTORS-703
> Project: ManifoldCF
> Issue Type: Improvement
> Components: Authority Service
> Affects Versions: ManifoldCF 1.3
> Reporter: Maciej Lizewski
> Assignee: Karl Wright
> Priority: Minor
> Fix For: ManifoldCF next
>
>
> If we deal with many auth sources there will be for sure need to map provided
> username to user id specific for particular auth source. As I remember - in
> book there is a note that this is the auth connector responsibility, but it
> means that in different scenarios we need different connectors (for example:
> in one scenario provided username is e-mail, in other - just login. You
> cannot use same auth connector in both cases).
> we should be able to configure "username mapper" for auth connector which may
> be simple regexp mapper or custom class providing mapping interface with more
> complex logic.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
