See follow-up comment below! text-based browser login does work. I will let the report remain open as this is good-faith use of the tool, and I think the poor quality of the interface with this method promotes development of a terminal-based login method.
Bug report
Describe the bug
The process of logging in from an HPC system is confusing. Only when the user Ctrl-C's out, are they given the URL which they can paste themself in the browser to succesfully login.
To Reproduce
Steps to reproduce the behavior.
From a Delftblue login node (which is and is incapable of popping out a browser window):
module load 2025 py-pip
python3.11 -m pip install pipx
pipx install qi
qi login # allow/reject the cookies until you land at the login page to understand login is not possible with this method.
Expected behavior
The client realizes that the terminal can not pop out a browser window.
It does not try to open a text-based browser, as this one does not work with the current authentication flow.
Alternatively, qi login should be able to read flags (--no-browser, --headless, --text-only) to allow a user to indicate no browser can be popped out and a URL should be provided for manual auth, or a command should be provided to login from this kind of system.
Operating System (please complete the following information)
- OS: Linux
- Version 8.10
- Distribution: RHEL
Additional context
Currently, when running qi login, the terminal runs a text-based-browser in the ssh-session. This one fails to authenticate the user, and after Ctrl-C'ing out gives the following:
qi login
/home/jremmen/.local/pipx/venvs/quantuminspire/lib/python3.11/site-packages/pydantic_settings/main.py:452: UserWarning: Config key `json_file` is set in model_config but will be ignored because no JsonConfigSettingsSource source is configured. To use this config key, add a JsonConfigSettingsSource source to the settings sources via the settings_customise_sources hook.
cls._settings_warn_unused_config_keys(sources, cls.model_config)
It is not necessary to specify the protocol in the URL. The protocol will be determined automatically.
Please continue logging in by opening: https://auth.quantum-inspire.com/activate?user_code=RPRF-FRVQ in your browser
If promped to verify a code, please confirm it is as follows: RPRF-FRVQ
Exiting via interrupt: 2
Following the link and verifying the code succesfully logs the client in.
See follow-up comment below! text-based browser login does work. I will let the report remain open as this is good-faith use of the tool, and I think the poor quality of the interface with this method promotes development of a terminal-based login method.
Bug report
Describe the bug
The process of logging in from an HPC system is confusing. Only when the user Ctrl-C's out, are they given the URL which they can paste themself in the browser to succesfully login.
To Reproduce
Steps to reproduce the behavior.
From a Delftblue login node (which is and is incapable of popping out a browser window):
module load 2025 py-pip python3.11 -m pip install pipx pipx install qi qi login # allow/reject the cookies until you land at the login page to understand login is not possible with this method.Expected behavior
The client realizes that the terminal can not pop out a browser window.
It does not try to open a text-based browser, as this one does not work with the current authentication flow.
Alternatively, qi login should be able to read flags (--no-browser, --headless, --text-only) to allow a user to indicate no browser can be popped out and a URL should be provided for manual auth, or a command should be provided to login from this kind of system.
Operating System (please complete the following information)
Additional context
Currently, when running
qi login, the terminal runs a text-based-browser in the ssh-session. This one fails to authenticate the user, and after Ctrl-C'ing out gives the following:Following the link and verifying the code succesfully logs the client in.