SSO fails working with Domain watch Passly v7.2.1

If you have configured Kaseya VSA for SSO following the setup 

VSA setup

VSA with Domain watch

When Passly v7.2.1 was released we patched a security issue that had an unintended side affect. Currently there is an issue if your users are trying to log into VSA from the SSO launchpad. The issue only replicates if VSA is setup with domain watch. This should only affect web-lunching the SAML application from the Passly Launchpad.

Specific issue:

  1. User is logged into Passly.
  2. User selects "Launchpad"
  3. User selects VSa app.
  4. User received a 500 error 




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