Content Access

With content access you can instruct agents from where to retrieve content. For example, a satellite server or a DFS share. When all endpoints fail, the primary zone servers will be used.

Content access can be configured at zone level or at context level. When configured at context level, the zone level configuration will be ignored.

URI

The URI defines the location of the endpoint. It can contain variables and has access to the special variable ${Content.ID}. The Content.ID variable contains the GUID of the content that is requested by the agent.

HTTP, HTTPS and SMB are the URI schemas that are supported. Use SMB for DFS and Windows shares. For example:

Variables can be used for the username and password. For example:

smb://${Content.Cred.Username}:${Content.Cred.Password}@dfs.liquit.com/workspace/content/${Content.ID}.dat

We advise marking the Content.Cred.Password variable sensitive, so it will not appear in any logging. When it is not possible to use variables, escape the username and password (Encode URI component).

For example

smb://liquit %5Ccontent:content-pwd@dfs.liquit.com/workspace/content/${Content.ID}.dat

You can use various tools to convert, like dencoder.

When using an HTTPS URI, make sure to use a valid certificate that is trusted by the Liquit Workspace Agent.

Priority

The endpoints will be tried in the order of their priority, from low to high. Load balancing (round robin) will be used between endpoints with the same priority.

Content Token

The content token is used to access content on a satellite server. This option must be enabled for satellite servers.