uberAgent

Configuring uberAgent Proxy Settings for LAS Licensing

April 22, 2026

Contributed by:

Citrix License Activation Service (LAS) requires uberAgent to establish outbound HTTP connections to specific Citrix LAS backends on the internet. While granting general internet access from all endpoints is often not possible due to security or compliance reasons, it is important to note that uberAgent only requires connections to specific, region-based targets. Unrestricted internet access is not required. By setting up a proxy that is limited to accept and forward connections to the Citrix LAS backends only, customers can efficiently operate uberAgent without granting full internet access to endpoints.

Starting with uberAgent 8.0, it is possible to configure the agent to use a proxy server for specific resources. This allows a secure setup where:

Endpoints do not have direct internet access.
All Citrix LAS licensing traffic is routed through a proxy.
The proxy only allows connections to the required LAS backends and blocks all other destinations.

Setting Up the Necessary Configurations

This article walks you through an example configuration for the use case described above, following the principles outlined here. Please note that setting up the proxy itself is not covered in this practice guide.

Identify Your Citrix LAS Backends

As a first step, you need to identify which LAS licensing backend is required in your environment. To do so, verify in which region your Citrix Cloud ID is based. As outlined in the firewall exclusions, Citrix operates multiple LAS backends for different regions. Choose from the following LAS backends based on the region of your Citrix Cloud ID.

Protocol	Target	Region
HTTPS	`https://api.cloud.com`	US, EU, APS
HTTPS	`https://api-us.cloud.com`	US, EU, APS
HTTPS	`https://api.citrixcloud.jp`	Japan

Note:

In this article, we assume that our Citrix Cloud ID is based in the US. Therefore, we are interested in the two URLs https://api.cloud.com and https://api-us.cloud.com. As mentioned before, a proxy can be configured so that it only permits outbound connections to the defined LAS backends and denies all other external destinations.

Configure Destination-to-Proxy Mappings

Now that the required LAS backends have been identified and the proxy is ready to process incoming requests, uberAgent has to be configured. To do so, open your uberAgent.conf and add the stanza [Proxy_List] including both targets. The configuration makes use of URL_REGEX. This means that the two URLs have to be converted into the appropriate syntax. Sticking with the example above and assuming our proxy server is proxy.customer.com, the configuration to add is:

[Proxy_List]
api\.cloud\.com = proxy.customer.com
api-us\.cloud\.com = proxy.customer.com
<!--NeedCopy-->

With the configuration shown above, only LAS-related communication is routed through the proxy; other HTTP communication, for example to on-premises backends, is not sent to the proxy.

Configure Proxy Authentication (optional)

If your proxy requires authentication, add the [Proxy_Auth] stanza to the configuration shown above:

[Proxy_Auth]
proxy.customer.com = user:password
<!--NeedCopy-->

Note:

uberAgent supports reading credentials as plain text, obfuscated via uAEncrypt, and from the operating system’s credential store. If uberAgent does not find authentication information in this stanza for a proxy that is configured in [Proxy_List], it will try to establish a connection without authentication.

Distribute the Configuration

As a final step, the updated uberAgent configuration (uberAgent.conf) has to be distributed to your endpoints. To do so, use one of uberAgent’s configuration options that best suits your needs.

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Was this helpful

Configuring uberAgent Proxy Settings for LAS Licensing

April 22, 2026

Contributed by:

April 22, 2026

Contributed by: