-
Notifications
You must be signed in to change notification settings - Fork 305
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Document options for accessing repositories that require authentication.
- Loading branch information
Showing
1 changed file
with
28 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
--- | ||
nav_order: 9 | ||
--- | ||
|
||
# Handling access to authenticated remote repositories | ||
{: .no_toc } | ||
|
||
1. TOC | ||
{:toc} | ||
|
||
|
||
There is no default concept of an "ostree server"; ostree expects to talk to a generic webserver, so any tool and technique applicable for generic HTTP can also apply to fetching content via OSTree's builtin HTTP client. | ||
|
||
## Using mutual TLS | ||
|
||
The `tls-client-cert-path` and `tls-client-key-path` expose the underlying HTTP code for [mutual TLS](https://en.wikipedia.org/wiki/Mutual_authentication). | ||
|
||
Each device can be provisioned with a secret key which grants it access to the webserver. | ||
|
||
## Using basic authentication | ||
|
||
The client supports HTTP `basic` authentication, but this has well-known management drawbacks. | ||
|
||
## Using cookies | ||
|
||
Since [this pull request](https://github.com/ostreedev/ostree/pull/531) ostree supports adding cookies to a remote configuration. This can be used with e.g. [Amazon CloudFront](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/private-content-signed-cookies.html). | ||
|
||
|