[
https://issues.apache.org/jira/browse/CONNECTORS-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695380#comment-13695380
]
Karl Wright commented on CONNECTORS-703:
----------------------------------------
I had what I think is a good idea for limiting the scope of human error that is
currently possible with the design I have now. Specifically one concern I've
had is that, for every authority connection, you will need to type in the
username domain in order for the authority to be able to find the user
information it needs.
Instead, I would like to propose that a mapping connector always take ONE input
and produce exactly ONE output. Furthermore, because a mapping connector's
name is unique, it is unnecessary to specify prerequisites explicitly; for both
authorities and mappers you just specify the name of the mapper whose output
you need, or <none> if you just want the input as passed into the UserACLs
servlet. The same mapper can still serve multiple authorities, keeping the
overall overhead low.
Maciej, would this satisfy your needs?
> 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
> 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
