External Portal

Cookies are used for reverse proxy authentication. In order for this cookie to be sent from the browser to the server under the correct conditions, it may be necessary to set the domain attribute of the cookie accordingly. For this purpose, the Reverse Proxy Auth Cookie Domain field has been added to the settings under User Authentication > External Portal > Settings.

Figure 1. User Authentication > External Portal > Settings

Input field	Description
Reverse Proxy Auth Cookie Domain	Cookies are used for reverse proxy authentication. To ensure that these cookies are sent from the browser to the server under the correct conditions, it may be necessary to set the domain attribute of the cookie accordingly. If this field is empty, the cookie domain is not explicitly set and corresponds to the domain or IP specification of the external portal. If the value has not been adjusted by the user, a sensible default value is used: No cookie domain when specifying an IP address The specified domain, if it is a second level domain (i.e. it is directly below a TLD, such as example.com) The next higher domain, if it is a subdomain. So for portal.example.com then e.g. example.com. The cookie domain is important so that successful authentication on the external portal hosted at portal.example.com, for example, is also effective for other services on other subdomains, such as webmail.example.com or intranet.example.com. For special cases, the cookie domain can be manually set to a custom value. Important: Important safety information: Setting a cookie domain causes the browser to send this cookie to the target server for requests to the specified domain. The cookie for reverse proxy authentication is sensitive information that enables the owner to access resources shared via reverse proxy. Only cookie domains that are fully trustworthy should be specified.

Input field

Description

Reverse Proxy Auth Cookie Domain

Cookies are used for reverse proxy authentication. To ensure that these cookies are sent from the browser to the server under the correct conditions, it may be necessary to set the domain attribute of the cookie accordingly. If this field is empty, the cookie domain is not explicitly set and corresponds to the domain or IP specification of the external portal. If the value has not been adjusted by the user, a sensible default value is used:

No cookie domain when specifying an IP address
The specified domain, if it is a second level domain (i.e. it is directly below a TLD, such as example.com)
The next higher domain, if it is a subdomain. So for portal.example.com then e.g. example.com.

The cookie domain is important so that successful authentication on the external portal hosted at portal.example.com, for example, is also effective for other services on other subdomains, such as webmail.example.com or intranet.example.com. For special cases, the cookie domain can be manually set to a custom value.

Important: Important safety information: Setting a cookie domain causes the browser to send this cookie to the target server for requests to the specified domain. The cookie for reverse proxy authentication is sensitive information that enables the owner to access resources shared via reverse proxy. Only cookie domains that are fully trustworthy should be specified.

Wireguard

A previously defined wireguard connection can now also be selected from the selectable connections.