[
https://issues.apache.org/jira/browse/CONNECTORS-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13675828#comment-13675828
]
Maciej Lizewski commented on CONNECTORS-703:
--------------------------------------------
current flow for getting user ACLs is:
HTTP call to userACLs servlet with username=XXX -> iterate through auth
connector -> call connector getAuthorizationResponse for username=XXX -> return
the response
this requires auth controllers to understand common username=XXX and map it to
user ID required in particular auth providers and this is not very flexible.
my proposition is to add mapper before calling getAuthorizationResponse which
could map username=XXX to some username=YYY which is more understandable by the
connector. This way auth connectors could be reusable in different scenarios
(depending on what can provided as initial username)
So the flow would look like:
HTTP call to userACLs servlet with username=XXX -> iterate through auth
connector -> map username=XXX to YYY -> call connector getAuthorizationResponse
for username=YYY -> return response
if you could configure such mappers in UI (like other components) - Manifold
would be much more flexible.
it is just an idea :)
> 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
