HaloPSA Ticketing Integration

Allowing ThreatLocker to access the Halo API

Within the HaloPSA portal, navigate to Configuration > Integrations > HaloPSA API > Applications.

Select 'New' located in the top right-hand corner to open the Add an Application window.

In the 'Details' tab:

• 1.  Enter a name for the application. 
• 2.  Select "Client ID and Secret (Services) under Authentication Method
  • The Client ID and Client Secret will be revealed. 
    • Please Note: The Client Secret will only be shown once.  Please copy and save both the Client ID and the Client Secret in a secure location. You will need these when setting up the integration inside the ThreatLocker portal.
• 3.  Select Agent from the 'Login Type' dropdown.
• 4.  Select the agent the integration should log in as in the 'Agent to log in as' dropdown.

In the 'Permissions' tab:

• Select the 'edit:tickets' permission to allow the integration to close tickets and 'read:customers' to allow the integration to gather a list of customers from HaloPSA. This list will be used to map HaloPSA customers to ThreatLocker organizations.

No changes are needed in the 'Security' tab.

Click the 'Save' button at the top of the window.

The newly created Application will be listed in the main 'Applications' list with the Client ID.  You will need this Client ID when configuring the integration inside the ThreatLocker portal.

Navigate back to Configuration > Integrations > HaloPSA API.

Copy the Resource Server and Authorisation Server addresses to use in the ThreatLocker Portal.

Setting up the HaloPSA Integration in the ThreatLocker Portal

Within the ThreatLocker Portal, navigate to the Integrations page. 

Input Halo into the search bar located in the top center of the page and select Halo from the list.

The 'Add HaloPSA Integration' sidebar will open.

1. Enter the 'Domain' address where the board is hosted.
2. Enter the 'Client ID' provided in the HaloPSA API > Applications list for the application created within the Halo portal for this integration.
3. Enter the 'Client Secret' provided within the Halo portal. Please note: If this Client Secret wasn't copied during creation of the application within Halo, you will need to edit the application in Halo and generate a new Client Secret.
4. In the 'Scope', enter/select the name of the permission(s) granted.

Click the blue 'Add' button in the bottom left corner.  

Company Mapping

Once the Details are saved, the "Company Mapping" tab will populate where sub organizations in ThreatLocker can be mapped to Halo Clients.

Select the 'Customer' in Halo on the left and the 'Organization' in ThreatLocker on the right, then press the blue '+' button to save the mapping. Continue until all desired Customers are mapped to ThreatLocker Organizations.

Ticket Settings

The 'Ticket Settings' tab is where all ticket settings can be specified.

1.  Ticket Type - This is the type of ticket you want specified in Halo when an Approval Request in ThreatLocker is raised.

2.  Status - This is the status you want tickets raised as in Halo.

3.  Escalation Status - For customers with Cyber Hero Management, if the heros need to escalate a request to you, this will be the status that escalated tickets are raised as.

4.  Auto Close Status - This will be status that once tickets in ThreatLocker change to this status, they are automatically closed in Halo.

5.  Priority - This is the priority that tickets will be raised with in Halo.

6.  Team - This is the Team in Halo that tickets will automatically be assigned to.

Be sure to click the blue 'Save' button to commit these changes.