Show who you are, the profile, the credential source and its expiry
Show the identity of the credential the selected profile uses (its own, or the default profile’s when that is the same server): the user, the profile, where the credential comes from (REPSY_TOKEN, the OS keyring or the plain file fallback), the kind of credential (a long-lived personal access token, or a 24 hour browser sign-in), the granted scopes and when it expires.
The server is asked who the credential belongs to (the access token endpoint for an access token, the profile endpoint for a session). The token itself is never printed; rp auth token does that on purpose.
Exit code 4 when there is no credential or the server rejects it.
rp auth status
Options inherited from parent commands
--api-url string Panel API URL of the profile, overrides the stored value
--ca-file string PEM file with extra trusted CA certificates
--debug Print debug output with secrets redacted
--hostname string Repsy host to use instead of the current profile
--insecure Do not verify TLS certificates (unsafe; plain http is chosen with the URL, not with this flag)
--insecure-storage Keep credentials in a plain 0600 file instead of the OS keyring (unsafe; a warning is printed once per command)
--jq string Filter JSON output with a jq expression (implies --output json)
--no-color Disable colored output
--no-input Never prompt; fail when input is needed
--output table|json|yaml Output format: table, json or yaml (default table; json when --jq is given)
--owner string Owner segment of Cloud protocol URLs; --owner= means none
--registry-url string Protocol host URL of the profile, overrides the stored value
--type os|cloud Product of the host, overrides detection
--web-url string Panel UI URL of the profile (where /cli/auth lives), overrides the stored value
--yes Answer yes to confirmation prompts
See also
- rp auth - Sign in to Repsy and manage the stored credential
Found a problem with this page?
Report a problem