Kaseya VSA 9 Integration

  Unify
  User activity monitoring

Kaseya VSA Integration Process

IMPORTANT: Only Kaseya VSA 9 is supported. Kaseya VSA 10 is not yet supported at this time. 

If you are currently utilizing IP restrictions in your firewall or within the product, please make sure to allow these IP addresses:

• 35.192.223.4
• 35.224.156.102

Prerequisites

• • Kaseya Domain/URL for your instance.
  • Credentials for a Kaseya User with permissions to create OAuth Clients within VSA
  • OAuth Client ID and Secret from VSA

Required Permissions

api/v1.0/system/orgs
api/v1.0/assetmgmt/agents
api/v1.0/assetmgmt/assets/{{agentId}}/customfields
api/v1.0/system/users
api/v1.0/environment
api/v1.0/system/logs
api/v1.0/assetmgmt/logs/{{agentId}}/*

Kaseya Domain/URL

You can obtain the Kaseya Domain/URL for your instance by copying it from the browser bar you use to connect to Kaseya.

Create an OAuth Client

1. Log into Kaseya VSA with a user with appropriate permissions for OAuth Client creation.
   
   
2. On the navigation bar, navigate to System\Server Management\OAuth Clients.
   
   
   
   
3. Click on Register Client.             
   
   
   
   
4. Fill out the Register Client window with the following information:
   Client Name: SaaS Alerts
   Redirect Url: https://manage.saasalerts.com/products/oauth2/redirect
   Email: Email to send the Client ID and Client Secret to
   
   
   
   
   
5. Copy the Client and Client Secret from the pop up, or check your email for the same information. Note: you will need to scroll over on the pop up to get the full Client Secret, as the window formatting may not show the entire Client Secret in its default view.
   
   
   
   
   Setup MSFT Entra ID for enhanced Unify functionality.
   
   Configure Unify functionality in SaaS Alerts.

Connecting SaaS Alerts to Kaseya VSA.

1. Find your MSP’s Organization in SaaS Alerts, or create a new Organization for your MSP. You can do that on the SaaS Alerts Organization page.

2. Click on Kaseya VSA in the list of products.

Note: you may receive an alert indicating that an existing Kaseya VSA integration already exists. Unless you have multiple instances of Kaseya, you should cancel, or you will have duplicate alerts created.

3. Populate the connection wizard with the Kaseya details you collected earlier. Here is an example:

4. Click Next.

5. A new window will appear that requires your Kaseya VSA credentials. Enter those credentials and your MFA response.

6. Click Allow on the Allow Access window.

7. You are now ready to configure Unify organization mapping.

Link to Unify How To KB 

FAQ

Why when connecting Kaseya VSA the Allow Access window pops up and then closes?

This issue is caused by a password manager filling in credentials automatically. Please use an incognito Google Chrome session with the password manager disabled and the allow screen will stay up and allow access. 

The user "SaaSAdmin" logged-in to my Kaseya VSA, did SaaS Alerts perform this action? 

No, we are using ClientID and Client Secret to get the tokens for your Kaseya VSA and we do not store any account credentials for the user "SaaSAdmin". We can confirm, the Kaseya support team can login to your RMM as a "SaaSAdmin" user.