Integrate Prisma Cloud with OpenShift
Table of Contents
Self.Hosted 22.06 (EoL)
Expand all | Collapse all
-
- Getting started
- System Requirements
- Prisma Cloud container images
- Onebox
- Kubernetes
- OpenShift v4
- Console on Fargate
- Amazon ECS
- Alibaba Cloud Container Service for Kubernetes (ACK)
- Azure Kubernetes Service (AKS)
- Amazon Elastic Kubernetes Service (EKS)
- Google Kubernetes Engine (GKE)
- Google Kubernetes Engine (GKE) Autopilot
- IBM Kubernetes Service (IKS)
- Windows
- Defender types
- Cluster Context
-
- Install a single Container Defender
- Automatically Install Container Defender in a Cluster
- App-Embedded Defender
- App-Embedded Defender for Fargate
- Default setting for App-Embedded Defender file system protection
- VMware Tanzu Application Service (TAS) Defender
- Serverless Defender
- Serverless Defender as a Lambda layer
- Auto-defend serverless functions
- Install a single Host Defender
- Auto-defend hosts
- Deploy Prisma Cloud Defender from the GCP Marketplace
- Decommission Defenders
- Redeploy Defenders
- Uninstall Defenders
-
- Rule ordering and pattern matching
- Backup and restore
- Custom feeds
- Configuring Prisma Cloud proxy settings
- Prisma Cloud Compute certificates
- Configure Agentless Scanning
- Agentless Scanning Modes
- Configure scanning
- User certificate validity period
- Enable HTTP access to Console
- Set different paths for Defender and Console (with DaemonSets)
- Authenticate to Console with certificates
- Configure custom certs from a predefined directory
- Customize terminal output
- Collections
- Tags
- Logon settings
- Reconfigure Prisma Cloud
- Subject Alternative Names
- WildFire Settings
- Log Scrubbing
- Clustered-DB
- Permissions by feature
-
- Logging into Prisma Cloud
- Integrating with an IdP
- Integrate with Active Directory
- Integrate with OpenLDAP
- Integrate Prisma Cloud with Open ID Connect
- Integrate with Okta via SAML 2.0 federation
- Integrate Google G Suite via SAML 2.0 federation
- Integrate with Azure Active Directory via SAML 2.0 federation
- Integrate with PingFederate via SAML 2.0 federation
- Integrate with Windows Server 2016 & 2012r2 Active Directory Federation Services (ADFS) via SAML 2.0 federation
- Integrate Prisma Cloud with GitHub
- Integrate Prisma Cloud with OpenShift
- Non-default UPN suffixes
- Compute user roles
- Assign roles
- Credentials store
- Cloud accounts
-
- Prisma Cloud vulnerability feed
- Vulnerability Explorer
- Vulnerability management rules
- Search CVEs
- Scan reports
- Scanning procedure
- Customize image scanning
- Configure Registry Scans
-
- Scan Images in Sonatype Nexus Registry
- Scan images in Alibaba Cloud Container Registry
- Scan images in Amazon EC2 Container Registry (ECR)
- Scan images in Azure Container Registry (ACR)
- Scan images in Docker Registry v2 (including Docker Hub)
- Scan images in Google Artifact Registry
- Scan images in Google Container Registry (GCR)
- Scan images in Harbor Registry
- Scan images in IBM Cloud Container Registry
- Scan images in Artifactory Docker Registry
- Scan images in OpenShift integrated Docker registry
- Trigger registry scans with Webhooks
- Base images
- Configure VM image scanning
- Configure code repository scanning
- Agentless scanning
- Malware scanning
- Vulnerability risk tree
- Vulnerabilities Detection
- CVSS scoring
- Windows container image scanning
- Serverless function scanning
- VMware Tanzu blobstore scanning
- Scan App-Embedded workloads
- Troubleshoot vulnerability detection
-
- Compliance Explorer
- Enforce compliance checks
- CIS Benchmarks
- Prisma Cloud Labs compliance checks
- Serverless functions compliance checks
- Windows compliance checks
- DISA STIG compliance checks
- Custom compliance checks
- Trusted images
- Host scanning
- VM image scanning
- App-Embedded scanning
- Detect secrets
- Cloud discovery
- OSS license management
- API
End-of-Life (EoL)
Integrate Prisma Cloud with OpenShift
OpenShift users can log into Prisma Cloud Console using OpenShift as an OAuth 2.0 provider.
Prisma Cloud currently supports OpenShift Platform versions 4.5 and older as an OAuth 2.0 provider.
We are working to add support for OpenShift versions 4.6 and later.
The OpenShift master includes a built-in OAuth server.
You can integrate OpenShift authentication into Prisma Cloud.
When users attempt to access Prisma Cloud, which is a protected resource, they are redirected to authenticate with OpenShift.
After authenticating successfully, they are redirected back to Prisma Cloud Console with an OAuth token.
This token scopes what the user can do in OpenShift.
Prisma Cloud only needs the auth token to get the user’s info (e.g. user name, email), and check the Prisma Cloud database to see if this user is authorized.
If so, Prisma Cloud creates a JWT token, with a role claim, to complete the authentication process to Console.
Roles are assigned based on users and group information specified in Console.
The following diagram shows the login flow when the auth provider is LDAP.
With LDAP, users enter their credentials in Prisma Cloud Console, and Prisma authenticates with the LDAP server on the user’s behalf.
With all other auth providers, Prisma isn’t part of verifying the user credentials
Instead Prisma redirects the client to the auth provider for authentication.
Once the user successfully authenticates via the authentication provider, the client is redirected back to Prisma Cloud Console with an object (SAML assertion for SAML, JWT token for OIDC, Access token for OAuth 2.0) that proves a successful login or, in the OAuth 2.0 case, gives us access to the application to verify the user identity.

Prisma Cloud supports the authorization code flow only.
Integrate Prisma Cloud with OpenShift
Configure Prisma Cloud so that OpenShift users can log into Prisma Cloud with the same identity.
- In OpenShift, register Prisma Cloud as an OAuth client. Set the redirect URL to:https://<CONSOLE>:<PORT>/api/v1/authenticate/callback/oauth.
- Log into Prisma Cloud Console.
- Go toManage > Authentication > Identity Providers > OAuth 2.0.
- SetIntegrate Oauth 2.0 users and groups with Prisma CloudtoEnabled.
- SetIdentity providertoOpenShift.
- SetClient IDto thenameof the OAuth client you set up in OpenShift.
- SetClient secretto thesecretin the OAuth client you set up in OpenShift.
- SetAuth URLtohttps://github.com/login/oauth/authorize.
- SetToken URLtohttps://github.com/login/oauth/access_token.
- InUser Info API URL, enter the TCP endpoint for the OpenShift API server. For example,https://openshift.default.svc.cluster.local.
- ClickSave.
Prisma Cloud to OpenShift user identity mappings
Create a Prisma Cloud user for every OpenShift user that should have access to Prisma Cloud.
After the user is authenticated, Prisma Cloud uses the access token to query OpenShift for the user’s information (user name, email).
The user information returned from OpenShift is compared against the Prisma Cloud Console database to determine if the user is authorized.
If so, a JWT token is returned.
- Go toManage > Authentication > Users.
- ClickAdd User.
- SetUsernameto the OpenShift user name.
- SetAuth methodtoOAuth.
- Select a role for the user.
- ClickSave.
- Test logging into Prisma Cloud Console.
- Logout of Prisma Cloud.
- On the login page, selectOAuth, and then clickLogin.
- Authorize the Prisma Cloud OAuth App to sign you in.
Prisma Cloud to OpenShift group mappings
Use groups to streamline how Prisma Cloud roles are assigned to users.
When you use groups to assign roles, you don’t have to create individual Prisma Cloud accounts for each user.
Groups can be associated and authenticated with by multiple identity providers.
- Go toManage > Authentication > Groups.
- ClickAdd Group.
- InName, enter an OpenShift group name.
- InAuthentication method, selectExternal Providers.
- InAuthentication Providers, selectOAuth group.
- Select a role for the members of the group.
- ClickSave.
- Test logging into Prisma Cloud Console.
- Logout of Prisma Cloud.
- On the login page, selectOAuth, and then clickLogin.
- Authorize the Prisma Cloud OAuth App to sign you in.