Configuring the Single Sign-On (SSO) integration with Parallels My Account

8 users found this article helpful

Integration between the Parallels My Account and corporate Identity Providers like Azure, Okta, or Ping Identity enables Single Sign-On (SSO) login to the Parallels My Account and automatic provisioning of the Parallels product licenses to the end-users in your Organization. The organization’s business account admins can login to using a standard corporate login procedure, while the end-users can activate the Parallels products on their devices via Single Sign-On.

Currently, the product activation via SSO is supported for Parallels Desktop for Mac Business Edition per-user subscriptions only and works with the Parallels Desktop for Mac version 18 or above.

But even if your organization does not use Parallels Desktop for Mac Business Edition, it may benefit from the SSO integration with My Account as it gives more control over the users who have access to the organization’s business account registered with Parallels, where the licensing assets are stored.

Once the integration is up and running, you can grant users access to your organization’s business account by adding them into the Parallels Business Account Admins group in your Identity Provider’s directory. If a user who was granted access leaves the organization and their account is deleted/blocked, it automatically deprives the user of access to Parallels My Account.

The integration between the Parallels My Account and a corporate identity provider uses protocols SAML 2.0 for SSO and SCIM 2.0 for synchronization of users identity information.

Refer to the following documents for details about configuring the integration for different identity provider platforms:



Ping Identity

If your Organization does not use Parallels Desktop for Mac Business Edition, just skip the parts of the instruction which describe configuring the Parallels Desktop for Mac user group.

Even if your corporate identity provider is not on the list (Azure, Okta, Ping Identity), you can try the integration assuming your provider supports SAML 2.0 and SCIM 2.0 protocols.

Was this article helpful?

Tell us how we can improve it.