Operation, Activation & Authentication

Modified on Mon, Jun 17 at 9:22 AM

Operation, Activation & Authentication

Below, you'll find some useful in regard to security & operation: 

 

  1. Whitelist our domains: @invarosoft.com and @itsp.invarosoft.com

 

  1. On top of that, to ensure the App works smoothly, make sure you also include in your white list the following addresses (note they are all HTTPS/443):

 

FOR AGENT OPERATION

  1. api.itspservice.net
  2. appcdn.itspservice.net
  3. mobui.itspservice.net
  4. requestevent.run
  5. myitportal.net
  6. goto.invarosoft.com

 

FOR FULL PRODUCT

  1. portal.invarosoft.net
  2. wizard.invarosoft.net

 

For deployment

Find the instructions here:  

 

For Activation:

You’ll find your activation codes attached. The updated list is here

 

 

For authentication, please note that:

It matches an AD user/local user with a PSA contact for the client the agent has been previously activated against. This process can be executed (1) by the user himself or (2) by the MSP without the user intervention. 

 

By the user himself

 

  • Option 1: Logging the first ticket (recommended)

When the user logs a ticket from an activated agent that has not been authenticated, the App will request the first name, last name & e-mail. If the third one matches a record in the database, the AD User/local user will be associated with it. 

If there is no match in the PSA, but the e-mail domain matches the client’s most common one, Invarosoft will create the contact in the PSA. 

 

Note that an e-mail confirmation is needed here. The end-user will receive a ‘Confirmation Required For Ticket’ e-mail, and a reaction is necessary for the contact creation/match to occur.

 

 

  • Option 2: Registering

In this scenario, the end-user right-clicks his IT icon and selects ‘login’

Then selects ‘register’ and provides First name, last name & e-mail

Once the user clicks ‘request password’, we’ll send him the credentials to authenticate himself. 

 

By the MSP without the end-user intervention


As an alternative to avoid end-user intervention for authentication, we’ve developed two ways for the MSP to make the match at their level.  

 

  • Option 3: Manual Assignment

Once an agent is activated, it’ll appear on the partner’s agent list in the gray bar, under agents >> agents. (https://portal.invarosoft.net/Client/Agents/0)

 

The partner needs to find the device and click the option ‘manage’. Once there, a list with each AD /Local User will appear, and clicking ‘assign user’ allows the partner to match that record with an existing PSA contact. 

 

  • Option 4: AD Harvester

Whenever the client has a single organizational unit on-premise Active Directory, with valid inputs for First Name, Last Name & E-mail, authentication can be automated through an extra piece of software for the server. It is available for our non-trial partners here: 

  1. Download Ad Harvester Exe Installer
  2. Download Ad Harvester Msi Installer

 

With its instructions to set it up, which are available here: 

 

And a video tutorial to do so, here: 

 

 

 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article