Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix docs #520

Merged
merged 1 commit into from
Jan 18, 2024
Merged

fix docs #520

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -267,11 +267,11 @@ See [Interactions](#interactions) for more examples.
It uses a oauth2 authentication model for interacting with the server.
Specifically the Device Authorization flow.

This must be set up using the command-line arguments:
This must be set up using the environment variables:

`--idp-url` pointing to your IdP where there must be an endpoint `{idp-url}/v1/token` for exchanging tokens.
`HAMCTL_OAUTH_IDP_URL` pointing to your IdP where there must be an endpoint `{idp-url}/v1/token` for exchanging tokens.

`--client-id` which is the oauth2 client id.
`HAMCTL_OAUTH_CLIENT_ID` which is the oauth2 client id.

`hamctl` will automatically initiate a login if you do not have a valid token on your system.
You can opt out of this behaviour by setting the environement variable `HAMCTL_OAUTH_AUTO_LOGIN=false`.
Expand Down
Loading