vacp2p/specs
1
0
Fork 0
mirror of https://github.com/vacp2p/specs.git synced 2026-01-09 21:17:58 -05:00
Code Issues Packages Projects Releases Wiki Activity

Clarify that server may ignore client initiated handshake and start server initiated one

Browse Source
This commit is contained in:
Marco Munizaga
2024-09-09 17:00:00 -07:00
parent ad8cd056d3
commit b51a4cc380
1 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
http/peer-id-auth.md
View File

@@ -187,7 +187,10 @@ protocol operates as follows:
The client initiated version of this handshake follows the same structure,
except that the client sends initially sends a `challenge-server` and the order
of who is authenticated first is reversed. The protocol is as follows
of who is authenticated first is reversed. The server MAY ignore the initial
request, and respond by starting the Server initiated handshake.
The client initiated handshake is as follows
1. The client makes an HTTP request to a known authenticated resource and sets
the header:
@@ -198,7 +201,7 @@ of who is authenticated first is reversed. The protocol is as follows
2. The server responds with status code 401 (Unauthorized) and set the header:
```
WWW-Authenticate: libp2p-PeerID challenge-client="<challenge-string>", opaque="<opaque-value>", public-key="<base64-encoded-public-key-bytes>", sig="<base64-signature-bytes>"
WWW-Authenticate: libp2p-PeerID challenge-client="<challenge-string>", public-key="<base64-encoded-public-key-bytes>", sig="<base64-signature-bytes>", opaque="<opaque-value>"
```
The `sig` param represents a signature over the parameters: