How to Remove Passly Software

 

Passly is/was AuthAnvil On-Demand

AuthAnvil On-Demand was released in Spring 2016. Kaseya via the ID Agent team announced on April 6th 2020 that AuthAnvil On-Demand was rebranded as Passly. This was published via the v7.0.0 release notes. This article guides you through the removal process of Passly endpoints.

This guide will also make sure you are not blocked from accessing any endpoints after removal of Passly from your environment. There are different types of agents: protection agents like RADIUS and Windows Logon agents and sync agents for Password Manager, Directory Sync & Advanced User Sync.

Walkthrough these steps to properly remove Passly. 

Step 1 – Help Us Help You
If you are removing Passly because of a problem, first give us a chance to fix it. You can contact support via the link the top right corner of the Helpdesk. 

Step 2 – Uninstall Agent Software
Windows Logon Agents
- You can disable the agent following this guide in an emergency.
RADIUS - This can be removed from Programs & Features as well as the appliance it was configured with.
Note: You will find removal directions for these agents via this guide
Passly DirSync (Directory Sync) - This can be removed from Programs & Features on the server where it was deployed. You can also simply run the installer again from an elevated command prompt (Run as Administrator) to trigger the removal of the agent. 
Passly AUSI (Advanced User Sync) - This can be removed from Programs & Features on the server where it was deployed. You can also simply run the installer agent again from an elevated command prompt (Run as Administrator) to trigger the removal of the agent.
Passly Password Sync agent - This can be removed from Programs & Features on the server where it was deployed. You can also simply run the installer agent again from an elevated command prompt (Run as Administrator) to trigger the removal of the agent.

Step 3 – Disabling RMM + PSA Integration
Most RMM and PSA tools have protection agents built into the respective management software.

VSA v9.1 - v9.5
- Please see this guide. This can be disabled under AuthAnvil Module > Configure AuthAnvil Settings.
- To disable Just 2FA Simple disable the Kaseya Logon Configuration.

- To disable just the SAML configuration you can de-select Enable Single Sign On to Kaseya.

- Once you have selected the feature you want to disable simply select Save settings and the integration is disabled.


BMS/Vorex
- Log into your account for Kaseya BMS/Vorex instance and select My company. Under Authentication. De-Select "Enable Single Sign on to Kaseya, save the settings and the SAML integration is disabled.

Autotask - Log into Autotask and select the Resources, here you can edit individual users(Resources) and disable AuthAnvil for 2FA.

3rd Party RMM & PSA Tools - We have posted some of the legacy setup guides here that might help with removal.

Step 4 - Disable SAML Integrations - In the SSO Manager there is several applications that could have been enabled. We recommend disabling all SAML integrations before completing your migration to another product. We have posted some of the legacy setup guides here that might help with removal.

Step 5 - Remove any OAuth 2.0 & OpenID Connect Integrations - Under the Auth Manager > Agents section you will see any configured endpoints. You will also need to disable the integrations in the host products before removal is compete. 

Step 6 - Disable SAS URL Integrations - There are several integrations that were historically configured with this custom URL  (https://companyname.my.passly.com/AuthAnvil/SAS.asmx / https://customer.my.authanvil.com/AuthAnvil/SAS.asmx) we recommend that all integrations using this URL be disabled. 

 

Have more questions?

Contact us

Was this article helpful?
0 out of 0 found this helpful

Provide feedback for the Documentation team!

Browse this section