From 2668ad3ce7132630232d9edf72f0b9f3306affb1 Mon Sep 17 00:00:00 2001 From: Knut Ahlers Date: Mon, 22 Apr 2019 13:57:21 -0400 Subject: [PATCH] Add documentation for @_authenticated --- Main-Configuration.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Main-Configuration.md b/Main-Configuration.md index 667a2b4..b38c78a 100644 --- a/Main-Configuration.md +++ b/Main-Configuration.md @@ -97,4 +97,6 @@ Each `rules` entry has two mandantory and three optional fields of which at leas - `regexp` - optional - String containing a regexp which must match the contents of the header selected by `field` - `equals` - optional - String which must fully match the contents of the header selected by `field` -The `allow` and `deny` directives are arrays of users and groups. Groups are prefixed using an `@` sign. There is a simple logic: Users before groups, denies before allows. So if you allow the group `@test` containing the user `mike` but deny the user `mike`, mike will not be able to access the matching sites. \ No newline at end of file +The `allow` and `deny` directives are arrays of users and groups. Groups are prefixed using an `@` sign. There is a simple logic: Users before groups, denies before allows. So if you allow the group `@test` containing the user `mike` but deny the user `mike`, mike will not be able to access the matching sites. + +A special group exists for all authenticated users: `@_authenticated`. This group does not need to be assigned to an user but automatically contains all logged in users. You can use that group in the `allow` directive to have all users with a valid login be able to access the resource. \ No newline at end of file