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
Copy file name to clipboardExpand all lines: docs/manual/access-control.rst
+20Lines changed: 20 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -151,6 +151,26 @@ For example, this header may be set based on IP range, or based on password auth
151
151
152
152
Further examples of how to set this header will be provided in the deployments section.
153
153
154
+
One may also specify default access for different users by adding sub keys to the ``default_access`` setting::
155
+
156
+
collections:
157
+
test:
158
+
...
159
+
default_access:
160
+
default: block
161
+
admin: allow
162
+
163
+
Note that the ``default`` entry will be applied both if the user name is empty and if it actually is ``default``.
164
+
If the ``default`` entry is missing, it will be assumed to be ``allow``::
165
+
166
+
collections:
167
+
test:
168
+
...
169
+
default_access:
170
+
guest: block
171
+
172
+
This works whether the ``default_access`` is specified at the top level or for a specific collection.
173
+
154
174
**Note: Do not use the user-based rules without configuring proper authentication on an Apache or Nginx frontend to set or remove this header, otherwise the 'X-Pywb-ACL-User' can easily be faked.**
155
175
156
176
See the :ref:`config-acl-header` section in Usage for examples on how to configure this header.
0 commit comments