[
https://issues.apache.org/jira/browse/CONNECTORS-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13689109#comment-13689109
]
Maciej Lizewski commented on CONNECTORS-703:
--------------------------------------------
That sounds also as acceptable solution, but it will be impossible to implement
that without breaking backward compatibility (auth connectors interface must
change to receive user record instead of user name). This is why I thought
about mappers - when you assume that there is 'identity mapper' (returning same
name it gets on input) used by default - compatibility will be maintained.
As for the use case - yes, you understand it well. We want single UI to search
documents in index authenticated against single auth center, and we would like
Manifold to map users from that center to a number of other centers configured
as auth connectors, and the mapping *can* be more sophisticated than cutting
domain after @ in provided username :)
> 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
