spring-projects / spring-projects/spring-security
SEC-1916: Exception Thrown During OpenID Authentication When User's Session Expires
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
Gary Jolly (Migrated from SEC-1916) said:
Please see "Spring Forum Reference" for origin of improvement request.
Because data that's important to the OpenID authentication process is stored in the session, if the user's session expires an exception is thrown. For example, the user got redirected to the login page but didn't enter their credentials right away (causes session to expire).
It would be nice to be able to use different strategies for saving the OpenID data needed during the authentication process. Right now, only the session is being used.
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 tracing the OpenID authentication flow and where its required data is stored in the user session. Determine the supported storage strategies and define how authentication should behave after session expiry; done means the exception is avoided and the chosen strategy works for the described login-delay scenario.
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
- 25/100