StableN/ASyncedN/A

Multiple New Portals with different branding for one customer [On-Prem]

Updated Mar 3, 2026649 viewsView on usehalo.com
  • New Portal

This outlines how to set up one customer to have multiple new web portals with different branding on each for On-Prem Customers

  1. Copy the \WebApp\portal\ directory into a new directory in the \WebApp\ folder. E.g. \WebApp\portal2
  2. Copy the appsettings.json file from the \Web App\ directory into the new directory, if it does not already exist.
    1. This will have the same auth and api URL as your main webapp appsettings file
  3. Create a new site from this new portal directory in IIS. 
  4. Import a certificate into IIS that covers the new portal URL, if one is not already installed.
  5. Create a HTTPS binding on the new portal site, selecting the covering certificate.
  6. In the web app - Go to Config > Integrations > Halo API > View Applications. Add a New Application with the following setup. Also ensure that "Allow Agent Logins" is switched to "no".

Authorisation Method = Authorisation Code.

Login Redirect URL = The new web portal url/portal/auth (e.g https://support.haloitsm.com/portal/auth)

Logout Redirect URL = The new web portal url/portal/ (e.g https://support.haloitsm.com/portal/)

Permissions = all

You can now setup branding on this page if using a multi-tenant organization structure by using the selections at the bottom of the page. 

5. Open the appsettings.json file you created earlier. Insert a line for "clientid_portal_override" and set it to your client id. Save. It should look similar to this. The api and authentication root values should not be changed.

{

    "api_root": "https://support.haloitsm.com/api",

    "authentication_root": "https://support.haloitsm.com/auth",

    "clientid_portal_override": "345e4af3-cbf5-42bf-8919-fe513ee36150"

}

The new portal should now work.