Skip to content

Editorial change to fix #71 #80

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 5, 2023
Merged

Editorial change to fix #71 #80

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions attacks-and-mitigations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -172,9 +172,9 @@ fragment and obtain the access token.

The complexity of implementing and managing pattern matching correctly obviously
causes security issues. This document therefore advises to simplify the required
logic and configuration by using exact redirect URI matching. This means
the authorization server MUST compare the two URIs using simple string
comparison as defined in [@!RFC3986], Section 6.2.1. The only exception are
logic and configuration by using exact redirect URI matching. This means the
authorization server MUST ensure that the two URIs are equal, see [@!RFC3986],
Section 6.2.1, Simple String Comparison, for details. The only exception are
native apps using a `localhost` URI: In this case, the AS MUST allow variable
port numbers as described in [@!RFC8252], Section 7.3.

Expand Down