Define the External Browser used for SAML authentication

[jumadeus]

Hello, I have been trying to figure out how to define which external browser is called for SAML authentication, as the CEF browser is not desired for deployment.
Regardless of which version of PCS, Pulse Desktop Client or Windows 10 is deployed it always calls an instance of Internet Explorer. The system's default browser was never set to IE to begin with and other (usable) browsers are present. Removing IE from the system causes the authentication to fail immediately.

The latest PCS and Client versions that I tested are 9.1R14

My apologies if this was already answered but I could not find a matching thread.

[zanyterp · Accepted solution]

you are correct, for windows it is IE and for macOS it is Safari. you are also correct that it cannot be changed.

[Mimmo]

Microsoft recently dismissed Internet Explorer. Is there any plan to change the default browser called by the Pulse Desktop Client?

[zanyterp]

yes, you can set edge as the browser used for external launch by setting a registry value (please see the 9.1R15 release notes for the information)

[[email protected]l.com]

We are running into a similar issue with MACOS using Safari as the browser, which doesn't support Yubikey. We have set Chrome as the default browser in the settings, which supports Yubikey. Is there an option to change the Pulse to use the default browser setting on the MACOS instead of using Safari by default?

[zanyterp]

no there is not
are you not seeing this render when you enable the option to use the pulse/ivanti embedded browser?