You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Jason Gerlowski (JIRA)" <ji...@apache.org> on 2019/07/15 19:48:00 UTC
[jira] [Created] (SOLR-13638) Add verbose debug/trace logging to
RuleBasedAuthorizationPlugin
Jason Gerlowski created SOLR-13638:
--------------------------------------
Summary: Add verbose debug/trace logging to RuleBasedAuthorizationPlugin
Key: SOLR-13638
URL: https://issues.apache.org/jira/browse/SOLR-13638
Project: Solr
Issue Type: Improvement
Security Level: Public (Default Security Level. Issues are Public)
Components: security
Affects Versions: master (9.0)
Reporter: Jason Gerlowski
Assignee: Jason Gerlowski
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
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org