From the user perspective, Pulse Secure client presents a clean, uncomplicated interface. The user can enter credentials, select a realm, save settings, and accept or reject the server certificate. When you configure the client, you can specify whether to permit end users to modify settings, such as by adding connections.
Security Assertion Markup Language (SAML) Authentication
Pulse environment can do SAML authentication for a Single Sign-on (SSO) in following two ways:
Pulse client will close the embedded browser, once the SAML authentication is done.
Note: If user resizes the Embedded browser window, size will remain same even if user reconnects to Pulse Desktop Client. Embedded browser window size will remain as pre-selected size which was set by the user for the first time, until user resizes it again.
Figure 3: SAML Authentication with Embedded browser
Figure 4 : SAML Authentication (External Browser)
The sign-in page is defined as part of the sign-in policy on the Pulse server and the Pulse client embeds the sign-in page within a Pulse client dialog box.
The client displays the connection status until the connection is made. If a connection fails as a result of the endpoint failing a Host Checker policy, Host Checker reason strings and remediation options appear.