spring-projects / spring-projects/spring-security

`@ClientRegistrationId` should support property placeholder resolution

Open
#19,592 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

in the following example, my.api works. but i cant use property placeholders from @ClientRegistrationid. it evaluates literaly.

@ClientRegistrationId( "${my.client}"  )
interface MyClient { 
 
 @GetExchange ("${my.api}") 
 String fetch() ;
}

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 tracing how @ClientRegistrationId is processed and compare it with the property-placeholder behavior shown for @GetExchange("${my.api}"). Verify the example with a configured my.client property, and consider the work done when the annotation resolves that placeholder instead of treating it literally.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spring
Domain
security
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.