Commit b4b2e83
committed
fix: place well-known discovery route per RFC 8414 3.1
The .well-known/oauth-authorization-server route was prefixed with the
issuer's base path *after* the well-known suffix (e.g.
/custom/path/.well-known/oauth-authorization-server), which RFC 8615 3
does not recognize as a well-known URI. RFC 8414 3.1 requires the
suffix to be inserted between the authority and the path component
instead: /.well-known/oauth-authorization-server/custom/path.
The /authorize, /token, /register, /revoke routes are unaffected -
they're plain URLs under the issuer's namespace, not well-known URIs.1 parent 92cb5f1 commit b4b2e83
2 files changed
Lines changed: 11 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
106 | 106 | | |
107 | 107 | | |
108 | 108 | | |
109 | | - | |
| 109 | + | |
| 110 | + | |
| 111 | + | |
| 112 | + | |
110 | 113 | | |
111 | 114 | | |
112 | 115 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
91 | 91 | | |
92 | 92 | | |
93 | 93 | | |
94 | | - | |
| 94 | + | |
| 95 | + | |
| 96 | + | |
| 97 | + | |
| 98 | + | |
95 | 99 | | |
96 | 100 | | |
97 | 101 | | |
| |||
100 | 104 | | |
101 | 105 | | |
102 | 106 | | |
103 | | - | |
| 107 | + | |
104 | 108 | | |
105 | 109 | | |
106 | 110 | | |
| |||
117 | 121 | | |
118 | 122 | | |
119 | 123 | | |
120 | | - | |
| 124 | + | |
121 | 125 | | |
122 | 126 | | |
0 commit comments