[
https://issues.apache.org/jira/browse/CONNECTORS-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687501#comment-13687501
]
Karl Wright commented on CONNECTORS-703:
----------------------------------------
What I'm stuck on here is the plug-in architecture proposed. I think a
username mapper would wind up being a first-class plugin, probably similar in
how it is managed to a connector or authority. You would want to have a UI
component as well, since configuration would be necessary.
So the proposal would be to build on IConnector and BaseConnector, as defined
in framework/core. New navigation links in the UI would be needed, and new
database tables - one for registering mappers, and another for including the
mapper configuration information. Determining the specific mappers, and the
order in which they are fired, might be specified in a standard tab for each
authority.
The problem to me is that this is a considerable amount of engineering work -
and the use case is not strong enough yet to justify it. What I'd need to get
over this hump is a scenario or two where an authority needed more than a
single potential mapping for the incoming user name. Otherwise, I think it's
better to stick with predefined, repository-specific mappings as we have now.
> 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 1.3
>
>
> 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
