Using content access, you can tell agents where to retrieve content. Examples include a satellite server or a DFS share. If all endpoints fail, the primary zone servers is used.
Content access can be configured at zone level (under Manage > Portal > Content Access) or you can overwrite it at the context level for specific identities.
For more information about how Application Workspace handles downloading the content and our recommendations, see Content Store.
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.
Example URIs
| Type | URI |
|---|---|
| Satellite | https://satellite.recastsoftware.com/api/v3/contents/${Content.ID}/$value |
| DFS share | smb://dfs.recastsoftware.com/workspace/content/${Content.ID}.dat |
Variables can be used for the username and password.
For example
smb://${Content.Cred.Username}:${Content.Cred.Password}@dfs.recastsoftware.com/workspace/content/${Content.ID}.dat
Recast recommends marking the Content.Cred.Password variable as 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.recastsoftware.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 Application Workspace Agent.
Priority
Endpoints are tried in priority order, 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. You'll need to enable this option for satellite servers.
