Avii/Radicale
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

Merge pull request #2174 from tendstofortytwo/add-groups-to-docs

Browse Source 
add documentation for `groups` in rights file
This commit is contained in:
Peter Bieringer
2026-07-02 08:37:50 +03:00
committed by GitHub
parent 69b265b539 b9327989ec
commit 50d8ee97a0
1 changed files with 11 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
DOCUMENTATION.md
View File

@@ -2562,6 +2562,13 @@ permissions: RW
user: .+ user: .+
collection: {user}/[^/]+ collection: {user}/[^/]+
permissions: rw permissions: rw
# Allow reading and writing the collection named "common" for people in
# certain LDAP groups
[groupcal]
groups: members,directors
collection: common
permission: rw
``` ```
The titles of the sections are ignored (but must be unique). The keys `user` The titles of the sections are ignored (but must be unique). The keys `user`
@@ -2569,6 +2576,10 @@ and `collection` contain regular expressions, that are matched against the
username and the path of the collection. Permissions from the first username and the path of the collection. Permissions from the first
matching section are used. If no section matches, access gets denied. matching section are used. If no section matches, access gets denied.
The `groups` key can be used to provide a comma-separated list of LDAP groups
which should be matched for access. In case a section has both `user` and
`groups`, either one matching will allow access in that section.
The username is empty for anonymous users. Therefore, the regex `.+` only The username is empty for anonymous users. Therefore, the regex `.+` only
matches authenticated users and `.*` matches everyone (including anonymous matches authenticated users and `.*` matches everyone (including anonymous
users). users).