oauth-as
Oauth Protected Resource Metadata By Path
Changed onThe RFC 9728 §3.1 location, which strict clients derive from the resource URI.
Restricted to the endpoints we actually protect: a catch-all would answer for any path and claim this API protects resources it does not serve.
get/.well-known/oauth-protected-resource/{resource_path}
Request
- The document declares no server URL.
- AuthHTTP bearer
Path parameters
resource_pathstring required
Response
Successful Response
unknown required
Changes
- info
endpoint added
- info