Is your feature request related to a problem? Please describe.
Currently in slicer 2.8.0-rc1 when you login to Prusa Connect it opens a window inside the application to allow authentication. This causes problems for workflows that involve password managers which then encourages users to open password managers externally copy and pasting credentials or possibly encouraging them to pick weak passwords.
This can also cause issues where authentication to third party vendors (such as Google login) where passkeys instead of passwords are used (especially true if the passkeys are stored in external password managers such as 1Password).
By allowing authentication via external browser, password managers built into browsers can be utilized (which most major password managers offer).
Describe the solution you'd like
An option in the UI to allow authentication to happen externally
Describe how it would work
If a user selects open authentication externally (either via a confirmation option or ideally on the auth screen itself) open the users browser, visit the url, allow the user to login, then intercept either OIDC or JWT or similar token via the app.
Additional context
Other applications that work with web auth intercepted via app include -
AWS Cli (when using something like aws sso login)
AWS VPN
Adobe suite of applications
Is your feature request related to a problem? Please describe. Currently in slicer 2.8.0-rc1 when you login to Prusa Connect it opens a window inside the application to allow authentication. This causes problems for workflows that involve password managers which then encourages users to open password managers externally copy and pasting credentials or possibly encouraging them to pick weak passwords.
This can also cause issues where authentication to third party vendors (such as Google login) where passkeys instead of passwords are used (especially true if the passkeys are stored in external password managers such as 1Password).
By allowing authentication via external browser, password managers built into browsers can be utilized (which most major password managers offer).
Describe the solution you'd like An option in the UI to allow authentication to happen externally
Describe how it would work If a user selects open authentication externally (either via a confirmation option or ideally on the auth screen itself) open the users browser, visit the url, allow the user to login, then intercept either OIDC or JWT or similar token via the app.
Additional context Other applications that work with web auth intercepted via app include - AWS Cli (when using something like aws sso login) AWS VPN Adobe suite of applications