Updating Workspace ONE Access Service FQDN in Enterprise Services application.properties Files

In an on-premises Workspace ONE Access service installation, if you change the fully-qualified domain name (FQDN) of the Workspace ONE Access service, you must also update the FQDN entry in the Directory Sync, User Auth, Kerberos Auth, and Virtual App services' application.properties files if you deployed these services before the FQDN change.

One of the scenarios in which you typically change the Workspace ONE Access service FQDN is when you place the Workspace ONE Access service virtual appliances behind a load balancer.

Procedure

1. Log in to the Workspace ONE Access connector server.
2. For each enterprise service (Directory Sync service, User Auth service, Kerberos Auth service, or Virtual App service) that is installed on the server, edit the INSTALL_DIR\Workspace ONE Access\enterpriseService\conf\application.properties file and make the following changes:
   • If you are editing the Directory Sync service application.properties file, update the Workspace ONE Access service FQDN in the following entry:

     eds.SAAS.endpoint=WorkspaceONEAccessServiceURL

     For example:

     eds.SAAS.endpoint=https://mysva.example.com

   • If you are editing the User Auth service application.properties file, update the Workspace ONE Access service FQDN in the following entry:

     eas.SAAS.endpoint=WorkspaceONEAccessServiceURL

     For example:

     eas.SAAS.endpoint=https://mysva.example.com

   • If you are editing the Kerberos Auth service application.properties file, update the Workspace ONE Access service FQDN in the following entry:

     eks.SAAS.endpoint=WorkspaceONEAccessServiceURL

     For example:

     eks.SAAS.endpoint=https://mysva.example.com

   • If you are editing the Virtual App service application.properties file, update the Workspace ONE Access service FQDN in the following entry:

     eis.SAAS.endpoint=WorkspaceONEAccessServiceURL

     For example:

     eis.SAAS.endpoint=https://mysva.example.com

3. Restart the Directory Sync, User Auth, Kerberos Auth, and Virtual App services.