OWASP ASVS 5.0 section 10.4.8 requires strict refresh token expiry, which conflicts with FAPI 2.0 SP 5.3.2.1-9
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 3
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
It says
10.4.8 Verify that refresh tokens have an absolute expiration, including if sliding refresh token expiration is applied.
(Source) OWASP ASVS 5.0 https://github.com/OWASP/ASVS/tree/v5.0.0#latest-stable-version---500
This is contrary to FAPI 2.0 Security Profile 5.3.2.1-9 that states "shall not use refresh token rotation except in extraordinary circumstances"
Contributor guide
No contributing guide indexed for this repository
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 comparing OWASP ASVS 5.0 section 10.4.8 with FAPI 2.0 Security Profile 5.3.2.1-9, the two references named in the issue. Determine whether the requirements genuinely conflict and document an agreed interpretation or specification change; completion depends on resolving that standards question.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100