[
https://issues.apache.org/jira/browse/CONNECTORS-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13689093#comment-13689093
]
Karl Wright commented on CONNECTORS-703:
----------------------------------------
Ok - so the use case is a client where they log in via one system, and that
login ID is translated to others subsequently by way of user metadata in
various systems?
What this sounds like it would need is, instead of a single user name, a user
name record, which gets (potentially) annotated by multiple systems along the
way. Then, authorities can look up whatever info they need about the user
identity from that record. The user lookup would be an ordered sequence of
plugins, while authorization lookup would be in parallel as it is today.
> 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
