{% extends "auth_base.html" %} {% block title %}My machines{% endblock %} {% block extra_scripts %}{% endblock %} {% block content %} Your account · machine access
Create one key per machine. Each machine can access your calculations; your browser password and authenticator stay in the browser.
{% if quota_limits %}Use this account's own machine key on the submitting computer. A VPN is not required when the configured public HTTPS endpoint is reachable.
Limits apply to your principal in this project across all machine keys. Zero blocks new work. An execution binding must be qualified before submission; this checklist does not run a target test. Already accepted jobs keep running.
{{ message }}
{% endif %} {% if issued %}Save this key privately on your machine. It is shown only once.
{{ issued }}
Allowed actions: {{ issued_key.scopes|join(', ') }}.
On the computer that will submit calculations, save vq-gateway-credentials.toml in Downloads. It contains your secret key. Install it with private permissions:
chmod 600 ~/Downloads/vq-gateway-credentials.toml
mkdir -p ~/.config/vq
(umask 077; set -C; cat ~/Downloads/vq-gateway-credentials.toml > ~/.config/vq/gateway-credentials.toml)
vq remote status
This works with released client v1.0.6 and newer. Installation refuses to overwrite an existing profile. Keep that profile or use vq remote status --credentials ~/Downloads/vq-gateway-credentials.toml. After successful installation and verification, remove the Downloads copy. Keep the key and file out of chat, source repositories and shared folders.
If your client has vq remote login, run vq remote login {{ gateway_url }} and paste the key at its hidden prompt.
This version supports submission and fetching, but predates remote login. Save the endpoint and the key shown above in a private ~/.config/vq/gateway-credentials.toml file:
url = "{{ gateway_url }}"
key = "PASTE_YOUR_MACHINE_KEY_HERE"
Create a new private file, then enter the endpoint and key inside the editor:
mkdir -p ~/.config/vq
(umask 077; set -C; : > ~/.config/vq/gateway-credentials.toml) && nano ~/.config/vq/gateway-credentials.toml
This refuses to overwrite an existing profile. Keep that profile or choose another file with --credentials FILE. After saving, set chmod 600 ~/.config/vq/gateway-credentials.toml, then run vq remote status to verify access. Keep the key out of shell commands and chat.
Your administrator needs to link this account to a submission identity before you can manage machine keys.
{% endif %} {% if not submission_enabled %}Submission from machines is not enabled for this account yet. Your administrator must configure and qualify its execution target.
{% endif %} {% if enabled %}Confirm your password and authenticator code before creating or revoking a key. You will return here to name your machine and choose an expiry.
{% endif %}Verify login to manage existing keys.
{% endif %} {% if gateway_url %}Submission endpoint: {{ gateway_url }}
Downloads are available only when a key is first created. An existing key's secret cannot be recovered. If you no longer have it, revoke that key and create a replacement for the intended machine; accepted calculations keep running.
{% for key in keys %}{{ key.key_id }}
Expires {{ key.expires_at or 'Never' }}
{{ 'Revoked' if key.revoked_at else 'Issued' }} · {{ key.scopes|join(', ') }}
Last used {{ key.last_used_at or 'Not yet used' }}
No machine keys issued.
{% endfor %} {% endblock %}