spring-projects / spring-projects/spring-security
Support Bearer Token Authentication of Introspection endpoint
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
Related to https://github.com/spring-projects/spring-security/issues/5200 and https://github.com/spring-projects/spring-security/pull/6352#discussion_r247270792
The OAuth 2.0 Introspection Response RFC allows a resource server to use a bearer token as authentication for an introspection request:
To prevent token scanning attacks, the endpoint MUST also require
some form of authorization to access this endpoint, such as client
authentication as described in OAuth 2.0 [RFC6749] or a separate
OAuth 2.0 access token such as the bearer token described in OAuth
2.0 Bearer Token Usage [RFC6750]. The methods of managing and
validating these authentication credentials are out of scope of this
specification.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the OAuth 2.0 Introspection Response RFC section linked in the issue, then review related issue #5200 and the discussion on pull request #6352. Done means the introspection endpoint supports bearer-token authentication while retaining the required authorization against token scanning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- api, authentication, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100