Liongard

Roar Users Guide & Documentation

Welcome! You'll find comprehensive guides and documentation to help MSPs start working with Liongard's Roar as quickly as possible, as well as support if you get stuck. Let's go #MakeITRoar!

Get Started    

SolarWinds N-central

👍

Quick Details

Typically Runs From: Managed Cloud Agent
Is Auto-Discovered By: N/A
Can Auto-Discover: SolarWinds N-central Child Inspectors
Parent/Child Type Inspector: Yes
Parent Inspector Returns Data: Yes
Inspection via: API
Data Summary: Here

Overview

See it in Action

Video isn't playing? Click here.

Inspector Description

The SolarWinds N-central Inspector is a dedicated Inspector for the SolarWinds N-central platform. This Inspector will bring back data such as:

  • Roles
  • Groups
  • Devices
  • Jobs

🚧

Multi-Service Organization Tenant Systems

If your SolarWinds N-central instance uses multiple Service Organizations, then create a user that only has access to the SO you would like to use to setup the Liongard Inspector.

Inspector Setup Preparation

The SolarWinds N-central Inspector requires a username and password to complete the setup. In the steps below, we will go over creating a new user, using the least amount of privileges needed to complete the integration setup, as well as creating a Read-Only role to assign to said user for setup. If you would like to, you may use an administrative account as long as it has the required permissions.

Step 1: Create a Read-only Role

  1. Create a Read-Only User Role. Under the SO level, navigate to Administrator > User Management > Roles > Create Role
  1. Assign your role a name and, if desired, a description. Use the drop-down on the right-hand side to set the following permissions as "Read Only":
  • Administration
  • Configuration
  • Devices
  • Tickets & Notifications

Save your changes at the bottom.

Step 2: Create a New User

  1. Next, we will create or use an existing user to apply the Read-only role we created above. Navigate to Administration > User Management > Users. Select the Create User button in the top left.

❗️

Multi Service Organizations tenant

If your instance utilizes multiple SO levels, then it is recommended that you create the user at the SO level so that it only accesses companies and sites under that SO.

  1. Fill out the required fields for user creation such a First Name, Last Name, Login Name, and Password. Complete these fields then select the Access Group Tab. Here you will need to assign an Access Group to the user, we recommend the default "All".

🚧

Access Groups

The API will only pull back information of the Companies, sites, SO, etc. in the Access group for which it is assigned, so using the default “All” group is preferred as it should adopt new companies as they are added.

  1. Next, select the *Roles Tab and Assign the Read-Only role we created in Step 1. Once you are done, save the user changes.

Step 3: Generate User Token

❗️

MFA Support

Currently, the SolarWinds N-central Inspector is unable to authenticate an account with MFA enabled. The Inspector must be configured with an Account that does not have MFA enabled.

SolarWinds enforces MFA on new accounts and has been retroactively enforcing MFA for some user accounts. If MFA is enforced on the account created for the Liongard inspector, MFA must be disabled for the inspection to complete successfully.

We will now proceed to generate a Token for the user instead of using Password. This provides a secure password to use with the API.

  1. Navigate to API Authentication under the User tab. Select Generate JSON Web Token.
  1. A window should pop up with the generated Token. Copy the Token and use it in thePassword field in the Liongard Inspector Setup process below.

Liongard Inspector Setup

Step 1: Parent Inspector Setup

Since SolarWinds N-central is a multi-tenant system where a single portal is used to manage many Environments, you will set up a single "Parent" Inspector with your username and password/Token that will then auto-discover "Child" Inspectors for each Environment.

In Liongard, navigate to Admin > Inspectors > Navigate to the SolarWinds N-central Inspector > Select Add System.

Fill in the following information:

  • Environment: Select your MSP's Environment
  • Friendly Name: Suggested Naming: [MSP Name] SolarWinds N-central Parent
  • Agent: Select CLOUD-LINUX
  • Inspector Version: Latest (Auto-Update)
  • Instance URL: This is the Domain and TLD of your SolarWinds N-central instance. For example if the instance name is "https://integration.n-able.com/IndexAction.action," then, the Instance URL is integration.n-able.com.
  • Username: Username of the API User
  • Password Password or API Token for the API User
  • Scheduling: The Inspector will default to run once a day at the time the Inspector is set up. Here you can adjust the schedule.

Select Save. The Inspector will now be triggered to run within the minute.

Step 2: Child Inspector Setup

After the first run of the Parent Inspector, your client SolarWinds N-central organizations will be Auto-Discovered and surfaced on the Discovered Systems page.

Navigate to the Discovered Systems tab in your Inspectors > SolarWinds N-central page

  • Activate your Discovered Systems by ensuring they're mapped to the correct Environment > Select the checkbox to the left of Inspector(s) > Select the Actions drop-down menu > Activate Launchpoints.
  • Users may also Archive Discovered Systems by Selecting the checkbox to the left of the Inspector(s) > Select the Actions drop-down menu > Archive Launchpoints.

Optional: Turn on Flexible Asset/Configuration Auto-Updating

If you would like this Inspector's data to be sent to ConnectWise and/or IT Glue, turn on Flexible Assets/Configurations for this Inspector:

  • ConnectWise: Admin > Integrations > ConnectWise > Configuration Types > Confirm the "Configuration Auto-Updating" toggle is enabled
  • IT Glue: Admin > Integrations > IT Glue > Flexible Assets > Confirm the "Flexible Asset Auto-Updating" toggle is enabled

Updated about a month ago


SolarWinds N-central


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.