Set up SSO Integration on Prisma Cloud
To secure administrator access to Prisma Cloud, go to your identity provider's site to configure single sign-on and then configure Prisma Cloud for SSO.
On Prisma Cloud, you can enable single sign-on (SSO) using an Identity Provider (IdP) that supports Security Assertion Markup Language (SAML), such as Okta, Azure Active Directory, or PingID. You can configure only one IdP for all the cloud accounts that Prisma Cloud monitors.
To access Prisma Cloud using SSO, every administrative user requires a local account on Prisma Cloud. You can either Add Administrative Users On Prisma Cloud to create the local account in advance of enabling SSO, or use Just-In-Time (JIT) Provisioning on the SSO configuration on Prisma Cloud if you prefer to create the local account automatically. With JIT Provisioning, the first time a user logs in and successfully authenticates with your SSO IdP, the SAML assertions are used to create a local user account on Prisma Cloud.
To enable SSO, you must first complete the setup on the IdP. Then, log in to Prisma Cloud using an account with System Admin privileges to configure SSO and redirect login requests to the IdP’s login page, so that your Prisma Cloud administrative users can log in using SSO. After you enable SSO, you must access Prisma Cloud from the IdP’s portal. Prisma Cloud supports IdP initiated SSO, and it’s SAML endpoint supports the POST method only.
As a best practice, enable a couple administrative users with both local authentication credentials on Prisma Cloud and SSO access so that they can log in to the administrative console and modify the SSO configuration when needed, without risk of account lockout. Make sure that each administrator has activated their Palo Alto Networks Customer Support Portal (CSP) account using the Welcome to Palo Alto Networks Support email and set a password to access the portal.
Also, any administrator who needs to access the Prisma Cloud API cannot use SSO and must authenticate directly to Prisma Cloud using the email address and password registered with Prisma Cloud.
- If you want to enable JIT provisioning for users, Create Prisma Cloud Roles before you continue to the next step. When you configure SSO on the IdP, you must attach this role to the user‘s profile so that the user has the appropriate permissions and can monitor the assigned cloud accounts on Prisma Cloud.
- Copy the Audience URI, for Prisma Cloud, which users need to access from the IdP.
- Log in to Prisma Cloud and select.SettingsSSO
- Copy theAudience URI (SP Entity ID)value. This is a read-only field in the format: https://app.prismacloud.io?customer=<string> to uniquely identify your instance of Prisma Cloud. You require this value when you configure SAML on your IdP.
- Set up the Identity Provider for SSO.
- This workflow uses Okta as the IdP. Before you begin to set up Okta configuration, login to your Prisma Cloud instance and copy the Audience URI (SP Entity ID) from Prisma Cloud. See For example: https://app.prismacloud.io/settings/sso.
- Login to Okta as an Administrator and clickAdmin.
- ClickAdd Applications.
- +Add Appsto create a new app.
- OnCreate a New Application Integration, selectWebforPlatformandSAML 2.0forSign on method.
- OnGeneral Settings, use these values and clickNext.App Name- Prisma Cloud SSO appApp Logo- Use the Prisma Cloud logoApp Visibility- Do not check these options
- ToConfigure SAML, specify theSign On URL.The format for Sign On URL uses the URL for Prisma Cloud, but you must replace app with api and add saml at the end. For example, if you access Prisma Cloud at https://app2.prismacloud.io, your Sign On URL should behttps://api2.prismacloud.io/samland if it is https://app.eu.prismacloud.io, it should behttps://api.eu.prismacloud.io/saml.
- ForAudience URI- Use the value displayed on Prisma Cloudthat you copied in the first step.SettingsSSO
- SelectName ID formatasPersistentandApplication usernameasOkta username.The value for the Name ID format must be set to persistent so that your IdP sends the same unique value for the NameID element in all SAML requests from a particular user. If you set it to anything else, the user will have a different saml:sub value for each session, and is not secure.
- SetUpdate application usernametoCreate and update.
- ForAdvanced Section, selectResponseasUnsigned,Assertion SignatureasSigned,Assertion EncryptionasUnEncrypted.These options ensure that the SAML authentication message are digitally signed by the IDP, and it restricts login to the SAML app only from browsers that have the signed certificate.
- (Required only for JIT provisioning of a local user account automatically on Prisma Cloud)Specify the attributes to send with the SAML assertion.
- Finish creating the app.You have now successfully created an application for the SAML integration. This application will have the details of theIdP URLandCertificatewhich you’ll need to add on Prisma Cloud to complete the SSO integration.
- Assign users or groups of users who can use the Prisma Cloud SSO app to log in to Prisma Cloud.Select Assignments on the app and, to add individual users.AssignAssign to PeopleYou can alsoAssign to Groups, to specify the groups to which your users are assigned. Groups are evaluated top down, which means users will be assigned to the first group in the order.
- (Required only for JIT provisioning of a local user account automatically on Prisma Cloud)Assign the role you created on Prisma Cloud to the user profile.
- Configure SSO on Prisma Cloud.
If the user is logged in already using a username/password and then logs in using SSO, the authentication token in the browser's local storage is replaced with the latest token.
- Log in to Prisma Cloud and select.SettingsSSO
- Enable SSO.
- Enter the value for yourIdentity Provider Issuer.This is the URL of a trusted provider such as Google, Salesforce, Okta, or Ping who act as your IdP in the authentication flow. On Okta, for example, you can find the Identity Provider issuer URL at.ApplicationsSign OnView Setup InstructionsIn the setup instructions, you have Identity Provider Issuer and Prisma Cloud Access SAML URL.
- Enter theIdentity Provider Logout URLto which a user is redirected to, when Prisma Cloud times out or when the user logs out.
- Enter your IdPCertificatein the standard X.509 format.You must copy and paste this from your IdP.
- Enter thePrisma Cloud Access SAML URLconfigured in your IdP settings.For example, on Okta this is the Identity Provider Single Sign-On URL. When you click this URL, after authentication with your IdP, you are redirected to Prisma Cloud. This link along with the Relay State Parameter is used for all the redirection links embedded in notifications like email, slack, SQS, and compliance reports.
- Relay State Param nameis SAML specific Relay State parameter name. If you provide this parameter along with Prisma Cloud Access SAML URL, all notification links in Splunk, Slack, SQS, email, and reports can link directly to the Prisma Cloud application. The relay state parameter or value is specific to your Identity Provider. For example, this value isRelayStatefor Okta.When using RelayState functionality, make sure your Prisma Cloud Access SAML URL corresponds to Identity Provider Single Sign-On URL ending in ‘/sso/saml’.
- (Optional)Clear theEnforce DNS Resolution for Prisma Cloud Access SAML URL.By default, Prisma Cloud performs a DNS look up to resolve the Prisma Cloud SAML Access URL you entered earlier. If your IdP is on your internal network, and you do not need to perform a DNS look up, you can clear this option to bypass the DNS lookup.
- (Optional)Enable Just-in-Time Provisioning for SSO users.Enable JIT Provisioning, if you want to create a local account for users who are authenticated by the IdP. With JIT, the user is provisioned with the first five roles mapped to the user’s profile on the IdP.
- Provide the user attributes in the SAML assertion or claim that Prisma Cloud can use to create the local user account.You must provide the email, role, first name, and last name for each user. Timezone is optional.
- SelectAllow select users to authenticate directly with Prisma Cloudto configure some users to access Prisma Cloud directly using their email address and password registered with Prisma Cloud, in addition to logging in via the SSO provider.When you enable SSO, make sure to select a few users who can also access Prisma Cloud directly using the email and password that is registered locally on Prisma Cloud to ensure that you are not locked out of the console in the event you have misconfigured SSO and need to modify the IdP settings. For accessing data through APIs, you need to authenticate directly to Prisma Cloud.
- Select theUserswho can access Prisma Cloud either using local authentication credentials on Prisma Cloud or using SSO.The users listed in the allow list can log in using SSO and also using a local account username and password that you have created on Prisma Cloud.
- Saveyour changes.
- Verify access using SSO.Administrative users for whom you have enabled SSO, must access Prisma Cloud from the Identity Provider’s portal. For example, if you have integrated Prisma Cloud with Okta, administrative users must login to Okta and then click on the Prisma Cloud app icon to be logged in to Prisma Cloud.
- UsingView last SSO login failures, you can see details of last five login issues or errors for SSO authentication for any users.
Recommended For You
Recommended videos not found.