lore login
Authenticate with the Lore registry using the OAuth 2.0 Device Authorization Grant (RFC 8628).
Usage
lore login [--registry <url>] [--org <slug>]Description
Opens a browser window to complete authentication with your identity provider. The CLI polls for the authorization code and stores the resulting token in the system keychain.
Flags
| Flag | Description |
|---|---|
--registry | Registry URL (default: https://registry.lore.infraestrutura.app) |
--org | Org slug. Routes login through that org’s custom identity provider instead of the default flow. |
Examples
# Login to the default registry
lore login
# Login to a self-hosted registry
lore login --registry https://registry.mycompany.com
# Login through an org's custom identity provider (e.g. Microsoft Entra ID)
lore login --org acme-corp--org requires the org to have a custom identity provider configured (Pro plan only). If the org has none, the CLI tells you so and suggests running lore login without --org.
Token Storage
The auth token is stored securely using the OS keychain:
- macOS: Keychain Access
- Linux: Secret Service (via libsecret)
- Windows: Windows Credential Manager
For CI environments, use the LORE_AUTH_TOKEN environment variable instead of lore login.