Enable SSO for Packmind Self-Hosted

Discover how Packmind can connect to your identity provider to comply with your security standards,.

This feature is only available for Packmind Enterprise subscription. Please get in touch with Packmind to get a quote or enable it.

Supported connections

Packmind is ready to use SSO enterprise providers:

• Azure AD

• Active Directory Federation Services (ADFS)

• Google Workspace

• Ping Identity (Ping One, Ping Federate)

• Keycloak

• IBM Security Verify Access

• SAML v2

• Okta

• OneLogin

Please also note we can enable on-demand the following SSO providers:

• ADP

• Auth0

• CAS

• Cloudflare

• Cyber Ark

• Duo

• ForgeRock

• JumpCloud

• NetIQ

• Rippling

• SalesForce

• Shibboleth

• VMware

Please reach us if your SSO Provider is not listed here.

Understand how SSO works with Packmind

Packmind relies on the Cryptr software for SSO authentication.

Solution 1: Use Cryptr Cloud

In this context:

• You'll rely on Cryptr Cloud and this requires that your Identity Provider is available outside your infrastructure (such as Google Workspace for instance).

• No data from Packmind will be sent or outside your network.

• Cryptr will store your Identity Provider data ; Packmind will not.

• Packmind will have to connect to an external domain name.

We can provide specific IP ranges or domain name if you want to add filtering.

Also, it is possible to set dedicated IPs for PCI compliance. Reach to know more.

Here is the schema on how things works:

To enable SSO in Packmind Self-Hosted:

1. You'll need to reach Packmind support to ask for SSO activation.

2. We'll ask you to provide an email address for your IT service/admin.

3. A link will be sent in order to start the configuration if the SSO settings.

You'll then have to go to Packmind Settings -> Authentication Mode.

Select `Single Sign-On` and fill these 4 values with the ones sent by the Packmind support.

If you need more information regarding security about Cryptr, reach us or visit the Cryptr trust center.

Solution 2: Deploy Crytpr on your infrastructure

In this context, you'll rely on a Cryptr version hosted in your own infrastructure (such as Google Workspace for instance).

So from the schema above, the only change in that Cryptr is hosted on your infrastructure.

To deploy Cryptr you'll have to use the Helm Chart available here.

Once it's deployed, reach Packmind support to get the procedure (will come soon here).

In case you prefer you to use Docker Compose, this is also possible.

Time-based one-time password (2FA)

This feature is in progress and will be released soon. Get in touch with us to get more information.