The following property groups are available for virtual proxies.
Identification
The Identification property group contains the basic virtual proxy properties in the Qlik Sense system.
All fields are mandatory and must not be empty.
| Property | Description | Default value |
|---|---|---|
|
Description |
The description of the virtual proxy. | Blank |
| Prefix |
The path name in the proxy’s URI that defines each additional path. Example: https://[node]/[prefix]/ You can only use characters that can be part of a URI path. You can use slashes (/), but the prefix cannot begin nor end with a slash. Hash signs (#) cannot be used. |
Blank |
| Session inactivity timeout (minutes) |
The maximum period of time with inactivity before timeout. After this, the session is invalid and the user is logged out from the system. |
30 minutes |
| Session cookie header name |
The name of the HTTP header used for the session cookie. This value is blank by default and you must enter a value. Tip noteIt can be useful to include the value of the Prefix property above as a suffix in the cookie name.
|
Blank |
Authentication
The Authentication property group contains the authentication method properties for the virtual proxies in the Qlik Sense system.
| Property | Description | Default value |
|---|---|---|
| Anonymous access mode |
How to handle anonymous access:
|
No anonymous user |
|
Authentication method |
|
Ticket |
| Header authentication header name |
The name of the HTTP header that identifies users, when header authentication is allowed. Mandatory if you allow header authentication (by selecting either Header authentication static user directory or Header authentication dynamic user directory for the Authentication method property). Information noteHeader authentication only supports US-ASCII (UTF-8 is not supported).
|
Blank |
| Header authentication static user directory |
The name of the user directory where additional information can be fetched for header authenticated users. Mandatory if you allow static header authentication (by selecting Header authentication static user directory for the Authentication method property). |
Blank |
| Header authentication dynamic user directory |
Mandatory if you allow dynamic header authentication (by selecting Header authentication dynamic user directory for the Authentication method property). The pattern you supply must contain ‘$ud’, ‘$id’ and a way to separate them. Example setting and matching header: $ud\\$id – matches USERDIRECTORY\userid (backslashes must be escaped with an additional \) $id@$ud – matches userid@USERDIRECTORY ($id and $ud can be in any order) $ud:::$id – matches USERDIRECTORY:::userid |
Blank |
| Windows authentication pattern | The chosen authentication pattern for logging in. | Windows |
| Authentication module redirect URI | When using an external authentication module, the clients are redirected to this URI for authentication. | Blank (default module, that is Windows authentication Kerberos/NTLM) |
| SAML host URI |
The server name that is exposed to the client. This name is used by the client for accessing Qlik services, such as the QMC. The server name does not have to be the same as the machine name, but in most cases it is. You can use either http:// or https:// in the URI. To be able to use http://, you must select Allow HTTP on the edit page of the proxy that the virtual proxy is linked to. Mandatory if you allow SAML authentication (by selecting SAML for the Authentication method property). |
Blank |
| SAML entity ID |
ID to identify the service provider. The ID must be unique. Mandatory if you allow SAML authentication (by selecting SAML for the Authentication method property). |
Blank |
| SAML metadata IdP |
The metadata from the IdP is used to configure the service provider, and is essential for the SAML authentication to work. A common way of obtaining the metadata is to download it from the IdP website. Click the browse button and open the IdP metadata .xml file for upload. To avoid errors, you can click View content and verify that the file has the correct content and format. The configuration is incomplete without metadata. |
|
| SAML attribute for user ID |
The SAML attribute name for the attribute describing the user ID.Name or friendly name can be used to identify the attribute. |
Blank |
| SAML attribute for user directory |
The SAML attribute name for the attribute describing the user directory. Name or friendly name can be used to identify the attribute.If the name value is enclosed in brackets, that value is used as a constant attribute value: [example] gives the constant attribute value 'example'. |
Blank
|
| SAML attribute mapping | Click Add new attribute to map SAML attributes to Qlik Sense attributes, and define if these are to be required by selecting Mandatory. Name or friendly name can be used to identify the attribute.If the name value is enclosed in brackets, that value is used as a constant attribute value: [example] gives the constant attribute value 'example'. |
Load balancing
The Load balancing property group contains the load balancing properties for the virtual proxies in the Qlik Sense system.
| Property | Description | Default value |
|---|---|---|
| Load balancing nodes | Click Add new server node to add load balancing to that node. | Blank |
Advanced
The Advanced property group contains the advanced properties for the virtual proxies in the Qlik Sense system.
| Property | Description | Default value |
|---|---|---|
|
Extended security environment |
Enabling this setting will send the following information about the client environment in the security header: OS, device, browser, and IP. If not selected, the user can run the same engine session simultaneously on multiple devices. |
Blank |
| Session cookie domain |
By default the session cookie is valid only for the machine that the proxy is installed on. This (optional) property allows you to increase its validity to a larger domain. Example:
|
Blank (default machine) |
| Additional response headers |
Headers added to all HTTP responses back to the client. Example:
|
Blank |
| Websocket origin white list | All values added here are validated starting from the bottom level. If, for example, domain.com is added, this means that all values ending with domain.com will be approved. If subdomain.domain.com is added, this means that all values ending with subdomain.domain.com will be approved. | Blank |
Integration
The Integration property group contains the integration properties for the virtual proxies in the Qlik Sense system.
| Property | Description | Default value |
|---|---|---|
| Session module base URI | The address to an external session module, if any. | Blank (default module, that is in memory) |
| Load balancing module base URI | The address to an external load balancing module that selects which Qlik Sense engine to use for the user’s session, if any. | Blank (default module, that is round robin) |
Tags
The Tags property group contains the available QMC tags in the Qlik Sense system.
| Property | Description |
|---|---|
| Tags |
Tip noteIf no QMC tags are available, this property group is empty.
Connected QMC tags are displayed under the text box. |
Custom properties
The Custom properties property group contains the custom properties in the Qlik Sense system. When a custom property has been activated for a resource, you can use the drop-down to select a custom property value.
| Property | Description |
|---|---|
| Custom properties |
If no custom properties are available, this property group is not displayed at all (or displayed but empty) and you must make a custom property available for this resource type before it will be displayed here.
|
Did this page help you?
If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!