Skip to content

Commit d48655a

Browse files
authored
Update JWT wording
Now using "JWT proof" consistently instead of "refresh JWT" or "request JWT"
1 parent 5adbc14 commit d48655a

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -155,10 +155,10 @@ POST /securesession/startsession HTTP/1.1
155155
Host: auth.example.com
156156
Accept: application/json
157157
Cookie: whatever_cookies_apply_to_this_request=value;
158-
Sec-Session-Response: registration JWT
158+
Sec-Session-Response: JWT Proof
159159
160160
```
161-
The JWT is signed with the newly created private key, and needs to contain the following values (the public key is in the [JWK](https://datatracker.ietf.org/doc/html/rfc7517) format):
161+
The JWT proof is signed with the newly created private key, and needs to contain the following values (the public key is in the [JWK](https://datatracker.ietf.org/doc/html/rfc7517) format):
162162
```jsonc
163163
// Header
164164
{
@@ -284,10 +284,10 @@ The browser replies to that response with a Sec-Session-Response header, contain
284284

285285
```http
286286
POST /securesession/refresh HTTP/1.1
287-
Sec-Session-Response: refresh JWT
287+
Sec-Session-Response: JWT proof
288288
```
289289

290-
The JWT contains:
290+
The JWT proof contains:
291291
```json
292292
{
293293
"jti": "challenge_value",

0 commit comments

Comments
 (0)