Authentication
JJHub supports two login methods and API token authentication for programmatic access.GitHub OAuth (Default)
The default and most common way to authenticate:Sign in with Key
Sign in with Key authentication is available via the JJHub web interface. It signs a message with your wallet - a secure passwordless login method. Sign in with Key is not available via the CLI. Use GitHub OAuth or an API token for CLI access.Credential Storage
After login, your credentials are stored in your OS keychain (macOS Keychain, Windows Credential Manager, or Linux Secret Service). For CI environments or systems without a keychain, use the--insecure-storage flag to store the token in a plain-text config file:
Check Authentication Status
Print Current Token
Log Out
API Tokens
For CI/CD pipelines and programmatic access, use personal access tokens. Tokens are created via the JJHub API or web interface (not via the CLI). Tokens are prefixed withjjhub_ and stored as SHA-256 hashes on the server - the full token is shown only at creation time.
Token Scopes
| Scope | Description |
|---|---|
repo | Full repository access (read + write) |
repo:read | Read repository contents |
repo:write | Push to repositories |
user | Full user access (read + write) |
user:read | Read user profile |
user:write | Update user profile |
admin | Full administrative access |
repo:write includes repo:read).
Environment Variables
JJHUB_TOKEN automatically. No config file needed for CI.
Alternatively, pipe a token directly: