PCCSE · Question #96
A customer has configured the JIT, and the user created by the process is trying to log in to the Prisma Cloud console. The user encounters the following error message: What is the reason for the erro
The correct answer is A. The attribute name is not set correctly in JIT settings.. Just-In-Time (JIT) provisioning in Prisma Cloud relies on SAML attribute mappings to automatically create and configure user accounts upon first login. If the attribute name configured in the JIT settings does not exactly match the attribute name being sent by the Identity Provid
Question
A customer has configured the JIT, and the user created by the process is trying to log in to the Prisma Cloud console. The user encounters the following error message:
What is the reason for the error message?
Exhibit
Options
- AThe attribute name is not set correctly in JIT settings.
- BThe user does not exist.
- CThe user entered an incorrect password
- DThe role is not assigned for the user.
How the community answered
(56 responses)- A88% (49)
- B2% (1)
- C7% (4)
- D4% (2)
Explanation
Just-In-Time (JIT) provisioning in Prisma Cloud relies on SAML attribute mappings to automatically create and configure user accounts upon first login. If the attribute name configured in the JIT settings does not exactly match the attribute name being sent by the Identity Provider (IdP) in the SAML assertion (e.g., a mismatch in the role attribute name), the provisioning process fails and the user sees an error. Option B (user does not exist) is not the root cause - JIT is specifically designed to create the user dynamically, so a pre-existing account is not required. Option C (incorrect password) is not applicable in SSO/SAML flows, which do not use a Prisma Cloud password. Option D (role not assigned) would be a consequence of an attribute mapping error, not a separate root cause.
Topics
Community Discussion
No community discussion yet for this question.
