Prisma Cloud SAML Configuration Bug

[fsuleman77]

The below is a Twistlock product related query, which I assume is a probable bug. As per the Twistlock and Azure AD SAML integration tested in the lab (per the Azure AD SAML document) and using the method of Prisma Cloud User to AAD User Identity mapping (not AAD Group mapping), an Application secret is not required to be filled for user identity mapping (ONLY required for group based, per the documentation).If I do not specify application secret, SAML settings doesn’t gets saved and throws an error.

1.Configuration

2.Error Refer below screenshot, when I try to save the SAML settings it gives the below error and doesn’t save configuration, till I input something in Application secret field. If i then try to give dummy secret, it saves the configuration successfully.

3.Documentation Refer section “Configure Prisma Cloud Console”

Per my understanding the application secret should not be required to be filled while using the Prisma Cloud User to AAD User Identity mapping method.