Hi there Pulse Community! We're working on integrating Pulse Secure Client with SAML 2.0 and Okta. We have it mostly working, but I had a question on the browser that the client uses. On most of our systems, we default their browser to Chrome, but they also have Legacy Edge (Soon to be Chromium Edge), & IE loaded on their system. When the Pulse Client attempt to do the SAML assertion, it pulls up Internet Explorer every single time. It doesn't appear to be a configurable setting.
What I'm trying to find out is
@robg3381 Pulse Client does have Embedded browser feature to take care of that.
If you have the latest Pulse client version (9.1Rx) and server version running 9.0Rx, then you should be seeing SAML embedded browser being used for SAML auths without any extra configuration.
My institution uses DUO two factor authentication which supports touch ID on macbook only in the chrome browser. It wont let me use touch ID when I try to use PCS. Is there any workaround so that PSC can open authentication in a chrome browser and allow touch ID?
Were you able to solve your issue with OKTA SAML authentication with Pusle? We are currently testing this in my company and it seems that the default embedded browser is stil IE11. Yubikey are not supported by IE11 hence we currently cannot do Okta MFA with our Yubikey on Pulse secure.