[
https://issues.apache.org/jira/browse/SOLR-13820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16946180#comment-16946180
]
ASF subversion and git services commented on SOLR-13820:
--------------------------------------------------------
Commit c9ba63dd2d8695655b89587b0b4fc670ea3f374b in lucene-solr's branch
refs/heads/branch_8x from Jason Gerlowski
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=c9ba63d ]
SOLR-13820: Improve RBAP documentation (#924)
The ref-guide page for Rule-Based Authorization was in need of a refresh. Some
mailing-list questions made it clear there were a few areas users were unclear
on, including permission resolution, permission syntax and defaults, and
pros/cons of editing configuration using the API vs directly in ZooKeeper.
This commit clarifies these points, as well as doing some larger restructuring
to (hopefully) make the page make a little more sense as a whole.
> Refresh Rule-Based Auth ref-guide page
> --------------------------------------
>
> Key: SOLR-13820
> URL: https://issues.apache.org/jira/browse/SOLR-13820
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: documentation
> Affects Versions: 8.2
> Reporter: Jason Gerlowski
> Assignee: Jason Gerlowski
> Priority: Minor
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> The Rule-Based Authorization page in the ref-guide could use some attention.
> * the layout could be more logical (currently permission syntax is covered as
> a digression under the Authorization API, etc.)
> * some relevant topics are missing altogether (permission-resolution ordering)
> * the permission syntax is missing a lot of description in terms of default
> values, special keys, etc.
> If this comes together quick enough, it'd be nice if we could get something
> better in front of users for 8.3
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
