[
https://issues.apache.org/jira/browse/CONNECTORS-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693842#comment-13693842
]
Karl Wright commented on CONNECTORS-703:
----------------------------------------
The basic UserACLs code is committed, and I've started working on the UI.
While I was doing so, it occurred to me that mapping prerequisites that I'd put
in place for Mapping Connections also might well apply to Authority
Connections. In other words, right now a Mapping Connection can specify that
it will not run until a specified list of other Mapping Connections is run.
For authority connections, there is currently an implicit "all mapping
connections must run first" constraint in place, but that could be replaced by
an explicit list, which could help throughput and parallelism.
> 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
