spring-projects / spring-projects/spring-security

Give SecurityFilterChain a name for tracing!

Open
#6,274 11 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

status: ideal-for-contribution
Dominant language
Java
Stars
9.6k
Forks
6.3k
Avg merge
2d 11h
Merged PRs (30d)
52

Description

Give SecurityFilterChain a name for debug tracing!

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 locating SecurityFilterChain and the debug tracing behavior in the Spring Security codebase. Read how filter chains are represented in tracing output and determine what naming information is expected. Done means the chain has a name available for debug tracing, with tests covering the behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spring
Domain
security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.