If your organization uses SAML, you may be able to configure Virtru authorization using your SSO resources. This article will cover configuration and how this will affect your end-users.
Configuring Virtru and SSO
For technical details on setting up SSO and Virtru, please visit Virtru SAML integration.
Virtru needs to enable this feature for your account before you start configuration. If you are interested in setting this up, please reach out to your Virtru Customer Success Manager or contact support.
Signing into the Dashboard with SSO
When signing into the Virtru Dashboard, users will see various options, including Use Single Sign-On (SSO):
Selecting the SSO option will route users to the email entry page:
If your team has configured Virtru and SSO, then users will be routed to their SSO solution after entering an email address from a configured domain:
If your team has not integrated Virtru and your SAML solution, users will see an error ("Email address not recognized") and will need to select Cancel to log in via a different pathway:
Once your user completes their standard SSO process, they will be routed to their Dashboard.
Activating Virtru products using SSO
Once Virtru and SSO are configured for your team, activating Virtru products via your SSO process will be seamless. During activation, configured accounts will automatically be routed to their SSO login pages before completing activations.
Gmail Browser Plugin
When a user needs to activate the Gmail plugin, they should see a prompt to Activate:
If SSO is configured, clicking Activate will open a new tab to complete sign in. If a user is already signed into SSO, the tab will automatically process and close, completing activation.
When configuring mobile apps, users should select their appropriate providers and enter their standard credentials. If SSO is configured, during the activation process, they will be routed to an SSO screen to complete the process:
Signing into the Secure Reader with SSO
For configured organizations, users will automatically be routed to their SSO page when selecting or manually entering their email address on the Secure Reader verification page.