Skip to content

Commit c593337

Browse files
committed
fix typo
1 parent de70195 commit c593337

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

draft-ietf-oauth-browser-based-apps.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -326,7 +326,7 @@ The attack ends when the access token expires or when a token is revoked with th
326326

327327
Note that the possession of the access token allows its unrestricted use by the attacker. The attacker can send arbitrary requests to resource servers, using any HTTP method, destination URL, header values, or body.
328328

329-
The application can use DPoP to ensure its access tokens are bound to non-exportable key held by the browser. In that case, it becomes significantly harder for the attacker to abuse stolen access tokens. More specifically, with DPoP, the attacker can only abuse stolen application tokens by carrying out an online attack, where the proofs are calculated in the user's browser. This attack is described in detail in section 11.4 of the {{DPoP}} specification. Additionally, when the attacker obtains a fresh set of tokens, as described in {{payload-new-flow}}, they can set up DPoP for these tokens using an attacker-controlled key pair. In that case, the attacker is again free to abuse this newly obtained access token without restrictions.
329+
The application can use DPoP to ensure its access tokens are bound to non-exportable keys held by the browser. In that case, it becomes significantly harder for the attacker to abuse stolen access tokens. More specifically, with DPoP, the attacker can only abuse stolen application tokens by carrying out an online attack, where the proofs are calculated in the user's browser. This attack is described in detail in section 11.4 of the {{DPoP}} specification. Additionally, when the attacker obtains a fresh set of tokens, as described in {{payload-new-flow}}, they can set up DPoP for these tokens using an attacker-controlled key pair. In that case, the attacker is again free to abuse this newly obtained access token without restrictions.
330330

331331

332332

@@ -1458,6 +1458,7 @@ Document History
14581458

14591459
* Applied editorial changes from Filip Skokan and Louis Jannett
14601460
* Clarified when cookie encryption applies
1461+
* Added a section with security considerations on the use of postMessage
14611462

14621463
-15
14631464

0 commit comments

Comments
 (0)