If you have configured Kaseya VSA for SSO following the setup
VSA with Domain watch https://helpdesk.kaseya.com/hc/en-gb/articles/4407406483473
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.
- User is logged into Passly.
- User selects "Launchpad"
- User selects VSa app.
- User received a 500 error