OWASP / OWASP/SecurityShepherd
SessionManagement4 should be somewhat easier
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.5k
- Forks
- 515
- Avg merge
- 3h 46m
- Merged PRs (30d)
- 1
Description
There is really no reason why session management 4 requires the user to try 21 different numbers before succeeding. A common feedback we get from our students is that we should lower this number. Having a high number just gives frustration and doesn't teach anything, people instead give up.
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 by locating the SessionManagement4 challenge and the value that requires 21 attempts. Read how that limit is enforced, then reduce it to an agreed lower number and verify that the challenge remains solvable with the expected student experience.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100