OIDC configuration on Prisma Cloud Enterprise failing for Azure Entra / Azure AD

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

OIDC configuration on Prisma Cloud Enterprise failing for Azure Entra / Azure AD

L2 Linker

I'm trying to configure our Prisma Cloud tenant to use OIDC SSO authentication. We're using Microsoft Entra ID (formerly Azure AD) as the identity provider. As far as I can say the flow works as expected going to Azure. I get transferred to our Microsoft tenant for login against our own AD,  I authenticate my user, and then I'm redirected back to the callback URL that is shown in the Prisma Cloud SSO configuration window. However, instead of being logged in to Prisma Cloud I get an error:

 

{"timestamp":"2023-12-14T12:19:22.961209Z","status":401,"error":"An error occurred while attempting to decode the Jwt: The ID Token contains invalid claims: {aud=[redacted-client-id]}","message":"bad_request","path":"GET:/authn/api/v1/oauth2/callback/<our-callback-uid>"}

redacted-client-id = the Client ID that I've configured in Prisma Cloud. The value in the error message matches the client id from the App registration in Azure, and also the value for Client id configured in Prisma Cloud. I've checked this several times, and also tested that the value has an effect by intentionally configuring the wrong client id in Prisma Cloud. In that case Azure complains immediately. So as far as I can tell the aud claim value should be correct. Anyone have any suggestions as to what could be going wrong here?

 

I've tried following the instructions here: https://docs.prismacloud.io/en/enterprise-edition/content-collections/administration/setup-sso-integ... but they are not very detailed in regards to what possibly has to be taken into account on the Azure side of things.

 

1 REPLY 1

L3 Networker

Please open a support case on this issue, the error message is calling out and issue with JWT token.  Please include a HAR file to assist the team with troubleshooting. 

  • 405 Views
  • 1 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!