spring-projects / spring-projects/spring-security

SEC-2346: Provide alternative ways of storing the SecurityContext

Open
#2,542 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type: enhancement type: jira
Dominant language
Java
Stars
9.6k
Forks
6.3k
Avg merge
2d 11h
Merged PRs (30d)
52

Description

Rob Winch (Migrated from SEC-2346) said:

It would be nice to provide additional implementations for SecurityContextRepository. Some ideas are:

  • stateless cookies
  • Nosql (i.e. Redis)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the SecurityContextRepository interface and its existing implementations in the Spring Security codebase. Compare the proposed stateless-cookie and NoSQL approaches, such as Redis, and determine the intended scope before changing anything. Done is not defined by the issue, so the implementation and acceptance criteria need clarification first.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spring
Domain
backend, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.