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.

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

Document path interpretation in auth config #142

Merged
merged 1 commit into from
Sep 13, 2023
Merged
Changes from all commits
Commits
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
5 changes: 5 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -278,6 +278,11 @@ Example for an authorization configuration that is used for the system tests:
"ca-certificate": "test-secrets/snakeoil-ca-1.crt"
}

Relative paths are interpreted with respect to the auth file, e.g. if the
example above is stored in /some/dir/kt-auth.json, `kt` will expect to find the
client certificate in /some/dir/test-secrets/kt-test.crt. You can disable this
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
client certificate in /some/dir/test-secrets/kt-test.crt. You can disable this
client certificate in /some/dir/kt-test.crt. You can disable this

behavior by using absolute paths in the configuration file.

### TLS one-way

Required fields:
Expand Down
Loading