[
https://issues.apache.org/jira/browse/CONNECTORS-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695386#comment-13695386
]
Maciej Lizewski commented on CONNECTORS-703:
--------------------------------------------
of course. it almost the same as I described :)
so just to make sure:
- you can define many mapping connectors similar to input/output/authority
connectors
- mapper has one simple function "String mapUsername( String fromUserName )"
(and probably some functions to manage connection and state like connect,
disconnect, check, etc)
- in authority connector you can select single mapper or leave this attribute
empty which means that connector will receive what was passed to UserACLs
- many authority connectors can read output from same mapper
it sounds really interesting!
> 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
