Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default Browser Failure #397

Closed
bagnaram opened this issue Jul 23, 2024 · 5 comments
Closed

Default Browser Failure #397

bagnaram opened this issue Jul 23, 2024 · 5 comments
Labels
bug Something isn't working default-browser

Comments

@bagnaram
Copy link

Describe the bug
Unable to use default browser for SSO. I see the following login error when using the default browser. The embedded browser doesn't support yubikeys so I wish to use my internal one.

Expected behavior
I expect to see the same page as in the internal browser.

Screenshots
image

Logs

  • For the GUI version, you can find the logs at ~/.local/share/gpclient/gpclient.log
  • For the CLI version, copy the output of the gpclient command.

Environment:

  • OS: Linux fedora 6.9.9-200.fc40.x86_64
  • Desktop Environment: Sway
  • bagnaram 3356 0.0 0.0 681592 9180 ? SLsl Jul22 0:00 /usr/bin/gnome-keyring-daemon --start --foreground --components=secrets

Additional context
Add any other context about the problem here.

@yuezk
Copy link
Owner

yuezk commented Jul 23, 2024

Looks like the authentication has already finished, you could have already used your yubikey. Retry it from the start for this error.

@bagnaram
Copy link
Author

It appears to be an issue launching in an already launched browser. It may be helpful to add a config option to override the browser with CLI args such as --profile in Firefox. I was able to get a successful login by temporarily installing a secondary browser and setting the XDG default browser to that browser instead of my main.

@yuezk
Copy link
Owner

yuezk commented Aug 1, 2024

Hi @bagnaram, glad you found the workaround, I will try to add an option to use a new profile.

@yuezk yuezk added the bug Something isn't working label Aug 1, 2024
yuezk added a commit that referenced this issue Aug 14, 2024
@yuezk
Copy link
Owner

yuezk commented Aug 16, 2024

Hi @bagnaram I found this may related to the sudo, even though I can launch the browser as a normal user. In 2.3.7, I enhanced the gpauth command to support the browser authentication. You can try the following command to authenticate the external browser and see if it works.

gpauth <portal> --browser default 2>/dev/null | sudo gpclient connect <portal> --cookie-on-stdin

And you can specify the browser to launch, e.g., --browser firefox or --browser chrome, etc.

@bagnaram
Copy link
Author

Thank you that option works for me using the separate browser instance!

@yuezk yuezk closed this as completed Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working default-browser
Projects
None yet
Development

No branches or pull requests

2 participants