← Integrations

Automated SSL certificate renewal for VMware Unified Access Gateway (Omnissa UAG)

Update and verify the certificate on every UAG.

Omnissa Unified Access Gateway (formerly VMware UAG) has a certificate on its Internet interface for Horizon clients and web apps. Each appliance behind your load balancer keeps its own copy. With public certificate lifetimes heading to 47 days, you'll have to update each gateway more often.

CertKit renews the certificate. The CertKit Agent uploads it through the UAG REST API and checks that the appliance serves the new certificate on port 443.

Start free trial Watch demo

Built for Unified Access Gateway

A pre-built Unified Access Gateway template ships in your CertKit account. No scripting required.

On every renewal, the agent signs in to the UAG REST API, confirms the account is an enabled administrator, and checks the appliance settings. If the Internet interface already serves the new certificate, it stops there. Otherwise it uploads the certificate as a PFX and checks port 443 until the appliance serves it with a trusted chain. The CertKit template uses an RSA certificate for the Internet interface.

Users connected through that appliance can drop when the certificate changes. Drain it from the load balancer first, deploy to one UAG at a time, and schedule those deployments for a maintenance window.

How to install an SSL certificate on VMware UAG

The manual process, if you want to do it yourself:

  1. Get the certificate as a PFX. Create the key and CSR, get the certificate signed, and bundle the certificate, key, and full chain into a password-protected PFX. Make sure the certificate covers the DNS name your clients use to connect.
  2. Sign in to the admin UI. Open the UAG admin UI on the management port (9443 by default) as an administrator, and choose Configure Manually.
  3. Upload it to the Internet interface. Under Advanced Settings, open TLS Server Certificate Settings. Apply it to the Internet Interface, set Certificate Type to PFX, upload the PFX with its password, and save.
  4. Check the appliance serves it. Connect directly to the appliance's Internet interface on port 443. Verify that it serves the new certificate and chain.
  5. Repeat on every appliance. Each UAG holds its own certificate. A pair behind a load balancer is two uploads, and a missed one serves the old certificate to whoever the load balancer sends there.

With public certificate lifetimes shrinking to 47 days, renewing a few weeks early means repeating this work about twelve times a year. If one gateway keeps an expired certificate, users can get certificate warnings or lose access to their Horizon desktops when the load balancer sends them there.

At 47 days, automation is the only sustainable way to run UAG certificates. Here's how CertKit does it.

Using CertKit to manage our public-facing SSL certificates has been an excellent decision. The platform is user-friendly, certificates are easy to deploy, and the automation agent streamlines the entire certificate lifecycle, eliminating concerns around shortening certificate validity periods.

Chris Austin, IT Engineer, Buckman

How it works

 Your network            CertKit                 ACME CA
┌───────────────────┐     ┌──────────────────┐    ┌─────────────┐
│  ┌─────────────┐  │     │                  │    │             │
│  │CertKit Agent├──┼────►│  Issue & Renew   │◄──►│             │
│  └──────┬──────┘  │     │   Certificates   │    │             │
│         │ REST    │     │                ┌───┐  └─────────────┘
│         │ :9443   │     └────────────────│DNS│
│         ▼         │                      └───┘
│  ┌─────────────┐  │
│  │ UAG (DMZ)   │  │
│  │ [x] Uploaded│  │
│  │ [x] Serving │  │
│  └─────────────┘  │
└───────────────────┘

CertKit issues and renews certificates centrally using delegated DNS validation. You create a one-time CNAME record, and CertKit handles every ACME challenge after that.

The CertKit Agent runs on a Windows host that can reach the UAG's management port and its Internet interface. It pulls each renewal from CertKit over outbound HTTPS, then signs in to the UAG REST API as a UAG administrator. The UAG password is stored encrypted in CertKit. The appliance never runs ACME or holds DNS credentials, and CertKit never connects into your network.

One appliance, several edge services

UAG runs several edge services side by side, and they don't all get their certificate from the same place. The CertKit template replaces the Internet interface certificate, the one the Horizon and web reverse proxy services present. Workspace ONE Tunnel and Content Gateway take theirs from the Workspace ONE UEM console, which pushes them to the appliance. CertKit doesn't touch those.

Internet interface Horizon and web reverse proxy. Replaced by CertKit on every renewal Admin interface The management UI and REST API on port 9443. Left as it is Tunnel and Content Gateway Set in the Workspace ONE UEM console. Left as it is

What CertKit handles

Setup takes about ten minutes

  1. Connect your domain. Add a one-time CNAME record to delegate DNS validation to CertKit.
  2. Prepare each UAG. An enabled administrator account that signs in with a password, one Internet certificate under TLS Server Certificate Settings, and both FIPS mode and SAML encryption certificate rollover off. The template defaults to JWT sign-in for UAG 2503 and later.
  3. Install the CertKit Agent. One command on a Windows host that can reach each UAG's management port and Internet interface, with .NET Framework 4.7.2 or later.
  4. Add the UAG deployment script. Add the Unified Access Gateway template once per appliance, with its management address, the account, and that appliance's own Internet address.

See the full architecture →

Unified Access Gateway deployment requirements and troubleshooting →

Why each appliance gets its own deployment

UAGs usually run in pairs or more behind a load balancer, and each appliance keeps its own copy of the certificate. A renewal script that checks the load balancer name can't tell which appliance answered. It can report success while the other one keeps serving the old certificate to every user the load balancer sends its way.

CertKit deploys to each appliance by its management address and checks it at the appliance's own Internet address. If verification fails, the deployment points you to the appliance to check.

UAG is just one part of your remote access

Behind most UAGs are VMware Horizon (Omnissa) Connection Servers with certificates of their own. Most organizations also give remote users more than one way in, through gateways like Citrix NetScaler, Ivanti Connect Secure, and Remote Desktop Gateway. CertKit automates all of it from one account.

See all integrations

Start automating UAG certificates today

Free 30-day trial. No credit card required. Direct access to our engineering team to get you set up.

Start free trial See pricing