You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Jason Gerlowski (Jira)" <ji...@apache.org> on 2019/09/20 19:12:00 UTC

[jira] [Resolved] (SOLR-13638) Add verbose debug/trace logging to RuleBasedAuthorizationPlugin

     [ https://issues.apache.org/jira/browse/SOLR-13638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Gerlowski resolved SOLR-13638.
------------------------------------
    Fix Version/s: 8.3
       Resolution: Fixed

> Add verbose debug/trace logging to RuleBasedAuthorizationPlugin
> ---------------------------------------------------------------
>
>                 Key: SOLR-13638
>                 URL: https://issues.apache.org/jira/browse/SOLR-13638
>             Project: Solr
>          Issue Type: Improvement
>          Components: security
>    Affects Versions: master (9.0)
>            Reporter: Jason Gerlowski
>            Assignee: Jason Gerlowski
>            Priority: Minor
>             Fix For: 8.3
>
>         Attachments: SOLR-13638.patch
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Every so often I find myself trying to understand why the {{RuleBasedAuthorizationPlugin}} rules in my security.json produce the results they do.  This would be much easier to troubleshoot if the class had logging (either under DEBUG, or TRACE) that was verbose enough to figure out what order rules were checked in, and why particular rules didn't match a given request.
> This jira covers adding logging that can help administrators better understand issues with their security.json.



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

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