You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow unauthenticated requests, mapped to a predefined user entry (#78)
* Anonymous user implementation
* Fallback to authenticated requests when accessing protected paths
* Update changelog.en.md
* Change name from anonymous_id to unauthenticated_username
* docs: add documentation for unauthenticated user configuration
* test: add tests for unauthenticated_username support
---------
Co-authored-by: sbogaart@pic.es <sbogaart@pic.es>
Co-authored-by: silviavandenbogaartmarzola <marzolasilvia3@gmail.com>
Copy file name to clipboardExpand all lines: docs/reference/config-file.en.md
+24Lines changed: 24 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,6 +25,7 @@ When the file exists, the mapping relationship is defined by the file content.
25
25
26
26
```json
27
27
{
28
+
"unauthenticated_username": "nobody",
28
29
"account_mapping": [
29
30
{
30
31
"username": "username",
@@ -40,6 +41,11 @@ When the file exists, the mapping relationship is defined by the file content.
40
41
"username": "guest",
41
42
"password": "password",
42
43
"permissions": []
44
+
},
45
+
{
46
+
"username": "nobody",
47
+
"password": "",
48
+
"permissions": ["+^/public"]
43
49
}
44
50
],
45
51
"http_basic_auth": {
@@ -75,13 +81,17 @@ When the file exists, the mapping relationship is defined by the file content.
75
81
}
76
82
```
77
83
84
+
**Note**: When `unauthenticated_username` is set and a user with that name exists in `account_mapping`
85
+
(typically with an empty password), requests with no authentication will be mapped to that user. Permissions of that user will determine allowed access for unauthenticated clients.
0 commit comments