How the Prisma Access Browser Extension Works
PABX initiates a login attempt every few minutes or when it detects a
change in the existing IdP session cookie. The process includes the following
steps:
IdP session Detection: When a user signs in to a business
application (such as a CRM) that integrates with their IdP, the browser
receives a session cookie that confirms the active session.
Active session Verification: During each login attempt, PABX
checks for valid session cookies from supported IdPs.
Domain Matching: If PABX detects an active session, it
checks whether the user’s domain (for example, company.com
in user@company.com) exists in the PABX
loginDomains configuration.
Silent Background Login: If the domain matches, PABX
silently attempts to authenticate in the background by accessing a
configured PAB application that integrates with the IdP. This typically
occurs when you set up the Cloud Identity Engine (CIE) during
on-boarding.
- Local Session Establishment: After successful authentication, PABX
creates a local session and enforces policy rules associated with the logged-in
user.
By using single sign-on (SSO), PABX enables users to access multiple
systems through a single login. This reduces sign-in effort and improves security by
centralizing credential management at the IdP level.