lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noble Paul (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-10814) Solr RuleBasedAuthorization config doesn't work seamlessly with kerberos authentication
Date Wed, 09 Aug 2017 06:52:00 GMT

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

Noble Paul commented on SOLR-10814:
-----------------------------------

bq.BTW I found that SecurityConfHandler in Solr does not support configuring top-level elements
of the security.json file 

correct and we need to add it

bq. Please include this fix in the Solr 7.0 branch as it will simplify the Solr/Sentry integration.

We have already frozen 7.0 branch. This can go in 7.1 which will be released pretty soon

> 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
>      Security Level: Public(Default Security Level. Issues are Public) 
>    Affects Versions: 6.2
>            Reporter: Hrishikesh Gadre
>
> 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 foo@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 foo@EXAMPLE.COM instead of foo. This is not good from usability perspective.   



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message