[ 
https://issues.apache.org/jira/browse/SOLR-10814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17146600#comment-17146600
 ] 

Mike Drob commented on SOLR-10814:
----------------------------------

I've been looking at this again, and have been thinking about the design a lot. 
I don't think that the shortName flag should be on coreContainer, that feels 
too broad. So I was trying to put it on the Auth plugin, as shown in my draft 
PR, but I am not sure that's right either. The PR isn't fully implemented yet 
anyway - the tests fail and there needs to be some more plumbing through the 
configuration options.

But maybe this makes sense on the authn plugin instead? The auth plugin 
shouldn't be tasked with figuring out where to find the user... it should be on 
the authentication plugin to create the correct principal in the first place?

> Solr RuleBasedAuthorization config doesn't work seamlessly with kerberos 
> authentication
> ---------------------------------------------------------------------------------------
>
>                 Key: SOLR-10814
>                 URL: https://issues.apache.org/jira/browse/SOLR-10814
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 6.2
>            Reporter: Hrishikesh Gadre
>            Priority: Major
>         Attachments: SOLR-10814.patch
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Solr allows configuring roles to control user access to the system. This is 
> accomplished through rule-based permission definitions which are assigned to 
> users.
> The authorization framework in Solr passes the information about the request 
> (to be authorized) using an instance of AuthorizationContext class. Currently 
> the only way to extract authenticated user is via getUserPrincipal() method 
> which returns an instance of java.security.Principal class. The 
> RuleBasedAuthorizationPlugin implementation invokes getName() method on the 
> Principal instance to fetch the list of associated roles.
> https://github.com/apache/lucene-solr/blob/2271e73e763b17f971731f6f69d6ffe46c40b944/solr/core/src/java/org/apache/solr/security/RuleBasedAuthorizationPlugin.java#L156
> In case of basic authentication mechanism, the principal is the userName. 
> Hence it works fine. But in case of kerberos authentication, the user 
> principal also contains the RELM information e.g. instead of foo, it would 
> return f...@example.com. This means if the user changes the authentication 
> mechanism, he would also need to change the user-role mapping in 
> authorization section to use f...@example.com instead of foo. This is not 
> good from usability perspective.   



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org

Reply via email to