| Filename | Latest commit message | Latest commit date |
|---|---|---|
d89e854133Previously the SSE connection would always default to the `/.well-known/oauth-protected-resource` URI, ignoring the `resource_metadata` portion of the `www-authenticate` returned in a 401. Extract the metadata from the initial 401, so RS servers with custom protected resource URIs (as in RFC9728, [section 3.1][1])) continue to work as expected. [1]: https://datatracker.ietf.org/doc/html/rfc9728#section-3.1 |
||
| .. | ||
| __mocks__ | ||
| client | ||
| examples | ||
| integration-tests | ||
| server | ||
| shared | ||
| cli.ts | ||
| inMemory.test.ts | ||
| inMemory.ts | ||
| types.test.ts | ||
| types.ts | ||