On-Prem Bindings & URLs
3 guides
Changing your Halo URLs
The article provides instructions for changing Halo agent and user portal URLs for on-premise installations. It requires access to IIS, the certificate store, SSL certificates, and DNS records configuration. Steps include updating IIS bindings with the new URL and corresponding certificate, configuring API and webapp URLs in Halo, and potentially updating the Self Service Portal config. Restarting the Halo site in IIS finalizes the update.
Multiple New Portals with different branding for one customer [On-Prem]
The article provides a step-by-step guide on setting up multiple web portals with different branding for an on-premise customer. It involves copying the portal directory, configuring IIS with a new site and certificate, and setting up app integrations with the appropriate authorization methods. Additional modifications to the appsettings.json file, including setting a client ID, are necessary to complete the portal setup and branding.
Updating On-Prem instance URL
To update the URL of an on-premise web application, ensure the HTTPS certificate for the new URL is installed on your web server and configure the DNS record to direct traffic to it. Set a HTTPS binding on the Halo site in IIS. Use the Config.exe in Halo to update API, AUTH, and Agent Web App URLs. Save changes, restart IIS, and clear cache using a specific URL if navigation issues arise.