You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/auth-flows.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@
3
3
If authentication is required, Julia uses [bearer tokens (RFC 6750)](https://datatracker.ietf.org/doc/html/rfc6750) to authenticate package server requests.
4
4
That is, the HTTP requests set the `Authorization: Bearer $(access_token)` header when fetching data from the package server.
5
5
6
-
The PkgAuthentication manages acquiring these tokens from package server, generally via an interactive flow.
6
+
PkgAuthentication.jl manages acquiring these tokens from package server, generally via an interactive flow.
7
7
This document describes the protocols related to the authentication,
8
8
and also acts as a specification for a few PkgAuthentication-specific conventions that _authenticated_ package servers should follow.
9
9
@@ -15,8 +15,7 @@ _Note: the discussions of the package server protocol itself (i.e. downloading o
Julia (i.e. Pkg.jl - the package manager) stores the token information in a `auth.toml` file in the "server directory".
19
-
For each package server host, it is generally stored as a TOML file at `~/.julia/servers/{hostname}/auth.toml`.
18
+
Julia (i.e. Pkg.jl - the package manager) stores the token information in a `auth.toml` file in the "server directory" at `~/.julia/servers/{hostname}/auth.toml`.
20
19
21
20
Pkg uses the following top-level key values pairs:
0 commit comments