spring-projects / spring-projects/spring-security

Add Support for customizing restOperations on OidcBackChannelLogoutHandler

Open Beginner friendly
#18,252 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Expected Behavior

We would like to set restOperations (RestTemplate) on OidcBackChannelLogoutHandler.

Current Behavior

Currently restOperations cannot be directly modified on OidcBackChannelLogoutHandler requiring us to copy the entire classes' source only to change restOperations.

Context

We need to customize this because we use locally signed certificates internally and do SSL offloading later, so when the Spring Boot app tries to call itself on localhost, it fails because it does not trust this locally signed certificate.

Of course there are workarounds for this problem such as configuring a JDK wide trust store but it would be really helpful to have native support for this especially considerung that the restOperations can be configured on other OIDC components as well.

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 with config/src/main/java/org/springframework/security/config/annotation/web/configurers/oauth2/client/OidcBackChannelLogoutHandler.java and inspect how its restOperations is initialized and used. Compare nearby OIDC components that already allow RestTemplate customization. Done means callers can provide custom restOperations for back-channel logout without copying the class, including support for locally signed certificates.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.