Feature Request: Open SSO Auth in Browser

[dvlogic]

+1 on this request too. It would allow better integration with 1Password. Alternatively, a tight integration directly with 1Password would also work.

[lix98755]

Another +1 for this feature request., although this thread has been quiet for a while. Any updates on this?

We have a similar use case where we are trying to set up Okta OIDC integration with Viscosity and Okta MFA. Right now, Viscosity does not work with okta verify or security keys (like yubikeys, passkeys, etc). With WebView, Okta verify leads to an infinite loop and the security keys option just errors out. Additionally, if we can open sso auth in browser, users who have active Okta sessions will not be asked to log in again.

[mheiland]

+1 since the current WebView solution breaks authentication with Passkeys or FIDO2 tokens. This works well with all major browsers and other VPN clients. It would be a shame if Viscosity would not support the latest and arguably greatest available authentication mechanisms.

[James]

Hi All,

The latest macOS beta version of Viscosity (1.12b1 at the time of writing) now supports web authentication taking place in the default web browser. This should make it easier to authenticate in situations where an associated domain cannot be set, but it does mean that Viscosity cannot perform further validation of the site being loaded. Information on how to update to the latest beta version can be found at:
https://www.sparklabs.com/support/kb/ar ... -versions/

For enterprise machines, setting an "associated domain" via MDM is still the recommended approach. This enables the use of WebAuthn (aka FIDO2 or Passkeys) authentication without the need for an external browser, however the associated domain must match that of both the domain being used for the WebAuthn Relaying Party ID, as well as for the website making the request (it's possible to have multiple associated domains).

Cheers,
James