Many organizations use SAML to authenticate users for web services. Prisma Cloud supports the SAML 2.0 federation protocol to access the Prisma Cloud Console. When SAML support is enabled, users can log into the Console with their federated credentials. This article provides detailed steps for federating your Prisma Cloud Console with your PingFederate v8.4 Identity Provider (IdP).
The Prisma Cloud/PingFederate SAML federation flow works as follows:
Users browse to Prisma Cloud Console.
Their browsers are redirected to the PingFederate SAML 2.0 endpoint.
They enter their credentials to authenticate. Multi-factor authentication can be enforced at this step.
A PingFederate SAML token is returned to Prisma Cloud Console.
Prisma Cloud Console validates the SAML token’s signature and associates the user to their Prisma Cloud account via user identity mapping or group membership.
Prisma Cloud Console is integrated with PingFederate as a federated SAML Service Provider. The steps to set up the integration are:
Logon to PingFederate
Go to IdP Configuration > SP Connection > Connection Type, and select Browser SSO.
Go to IdP Configuration > SP Connection > Connection Options, and select Browser SSO Profiles SAML 2.0.
Skip the Import Metadata tab.
Go to IdP Configuration > SP Connection > General Info.
In Partner’s Entity ID, enter twistlock.
|By default, the Partner’s Entity ID is "twistlock". When configuring the SAML Audience in the Prisma Cloud Console, the default value is "twistlock". If you choose a different value here, be sure to set the same value in your Console.|
In Connection Name, enter Prisma Cloud Console.