OWASP / OWASP/SecurityShepherd
Bad OAuth Implementation Level
Open
Nobody has claimed this yet.
Levels
Mobile
- Dominant language
- Java
- Stars
- 1.5k
- Forks
- 515
- Avg merge
- 3h 46m
- Merged PRs (30d)
- 1
Description
Note sure how to implement, but would be a good one
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
No files, tests, or implementation details are named. Start by locating the existing security training levels and any OAuth-related entry points, then determine the intended challenge scope and acceptance criteria. Done means the OAuth level is implemented with appropriate tests and documented expected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100