docs: npm custom locations (#4152)

pull/4153/head
James Elliott 2022-10-09 12:09:45 +11:00 committed by GitHub
parent ab2bcfd677
commit 644616d8b1
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 21 additions and 0 deletions

View File

@ -131,6 +131,8 @@ either most likely require an adjustment, or may require an adjustment if you're
* You are running Authelia on the default port.
* You are running Authelia with the `container_name` of `authelia` or the Authelia process is otherwise resolvable by
[NGINX Proxy Manager] as `authelia`.
* If you want to use a [Custom Location](#protected-application-custom-locations) and wish for it to be protected you
follow the [Protected Application Custom Location](#protected-application-custom-locations) guide.
### Snippets
@ -206,6 +208,25 @@ Protected Application (Nextcloud) `Advanced` tab example:
{{< figure src="protectedapp.advanced.png" alt="Step 4" width="450" >}}
### Protected Application Custom Locations
It's important to note if you define locations in the `Custom Locations` tab of a proxy host that they will not be
checked with Authelia for authorization effectively bypassing the authorization policies you implement. If you want a
custom location then you can also define this in the advanced tab.
To replicate the `Custom Location` tab below a location block can be *__ADDED__* to the
[Protected Application](#protected-application) `Advanced` tab:
```nginx
location /custom {
include /snippets/proxy.conf;
include /snippets/authelia-authrequest.conf;
proxy_pass http://192.168.1.20:8080;
}
```
{{< figure src="protectedapp.customlocation.png" alt="Custom Location" width="450" >}}
#### Proxy Hosts Screenshot
The following screenshot shows an example of following the directions for the Authelia Portal and two applications:

Binary file not shown.

After

Width:  |  Height:  |  Size: 15 KiB