[
https://issues.apache.org/jira/browse/CONNECTORS-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13675837#comment-13675837
]
Karl Wright commented on CONNECTORS-703:
----------------------------------------
Ok, I think your proposal makes sense (and I think I actually got it right
before too).
Authority writers are told to expect the username to be given to their
authority in the form "user@domain". This represents a tacit acknowledgement
that most user names come from Active Directory. The proposal here will, in
some sense, make ManifoldCF more general - but will also change this
expectation. So I have to think through how it would be thought about, and
what authority writers should do.
> add username mappers functionality
> ----------------------------------
>
> Key: CONNECTORS-703
> URL: https://issues.apache.org/jira/browse/CONNECTORS-703
> Project: ManifoldCF
> Issue Type: Improvement
> Components: Authority Service
> Reporter: Maciej Lizewski
> Priority: Minor
>
> 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
