Package: iqm-cortex-cli
Cortex CLICommand-line interface (CLI) for managing user authentication when using IQM quantum computers.Installing Cortex CLIRequirements for installing:Python 3.9-3.11pip$pipinstalliqm-cortex-cliUsing Cortex CLIFor general usage instructions, run$cortex--helpInitializationFirst, Cortex CLI needs initialization, which produces a configuration file:$cortexinitCortex CLI will ask a few questions. You can also pass the values via command line to avoid having an interactive
prompt. Seecortex init--helpfor details.LoginTo log in, use$cortexauthloginThis will ask you to enter your username and password. If you have a temporary password you will be asked to go to the
authentication server and enter a new password. URL of the authentication server will be provided.After a successful authentication, tokens will be saved into a tokens file (path specified in the configuration file),
and a token manager daemon will start in the background. Token manager will periodically refresh the session and
re-write the tokens file.To use the token manager in a foreground mode (not as daemon), runcortex auth login--no-daemon. This requires
keeping the shell session alive. However, you can start the process in the background by adding&after the
command:cortex auth login--no-daemon&. This applies to Bash, zsh and similar shells, but may not be available
on all shells.To login and get tokens once, without starting a token manager at all, runcortex auth login--no-refresh.If the tokens file already exists, then runningcortex auth loginwill first attempt to refresh the session without
asking you for a username and password. If that fails (because existing tokens may already have expired), you’ll be
asked to re-enter your credentials.Seecortex auth login--helpfor more details.Use with Cirq on IQM, Qiskit on IQM, etc.Adapters based on IQM Client, such as Cirq on IQM and Qiskit on IQM, can take advantage of the tokens file maintained by
Cortex CLI. This way you won’t need to provide the authentication server URL, username, or password to the adapter
library itself. To achieve this, follow the instructions printed on the screen after runningcortex auth login.
Namely, set theIQM_TOKENS_FILEenvironment variable to point to your tokens file.On Linux:$exportIQM_TOKENS_FILE=/home/<username>/tokens.jsonOn Windows:setIQM_TOKENS_FILE=C:\Users\<username>\.cache\iqm-cortex-cli\tokens.jsonOnce set, this environment variable is read by the instance of IQM Client associated with the adapter. As a result,
from the point of view of the adapter it looks like authentication is simply not required (i.e. no
authentication-related information has to be provided to the adapter).StatusTo see the current status of the token manager, use:$cortexauthstatusIf the tokens file exists,cortex auth statuswill report whether the corresponding token
manager is running. It will also print the time of the last successful refresh request, and
how much time is left until current tokens expire.Seecortex auth status--helpfor more details.LogoutTo log out, run$cortexauthlogoutThis will send a logout request to the authentication server, kill the token manager daemon (if any), and delete the
tokens file.You may want to stop the token manager, but maintain the session on the server and keep the tokens file intact.
To do so, run:$cortexauthlogout--keep-tokensSeecortex auth logout--helpfor more details.Multiple configuration filesBy default, all Cortex CLI commands read the configuration file from the default location~/.config/iqm-cortex-cli/config.json. You can specify a different filepath by providing the--config-filevalue,
for example:$cortexauthstatus--config-file/home/joe/config.json$cortexauthlogin--config-file/home/joe/config.json$cortexauthlogout--config-file/home/joe/config.json