SWI-3723 [Snyk] Security upgrade org.springframework.security:spring-security-oauth2-client from 5.7.8 to 7.0.0

[bwappsec]

Snyk has created this PR to fix 1 vulnerabilities in the maven dependencies of this project.

Snyk changed the following file(s):

• samples/openapi3/client/petstore/spring-cloud-http-basic/pom.xml

---

This is a major version upgrade from Spring Security 5.x to 7.x, which introduces significant breaking changes and requires a Java 17 baseline. [7] The entire security configuration needs to be rewritten due to the removal of WebSecurityConfigurerAdapter in favor of a component-based SecurityFilterChain bean approach. [2, 4, 6]

Key breaking changes include:

• Configuration Rewrite: WebSecurityConfigurerAdapter is removed. You must now define a SecurityFilterChain bean. [6, 7]
• API Changes: authorizeRequests() is replaced by authorizeHttpRequests(), and antMatchers() is replaced by requestMatchers(). [2, 6]
• Lambda DSL: Configuration using lambda expressions is now mandatory, and the .and() method for chaining has been removed. [1, 22]
• Namespace Migration: The project now uses the jakarta.* namespace instead of javax.*. [7]

Source: Spring Security Documentation
Recommendation: This upgrade requires significant code refactoring. It is highly recommended to first migrate to Spring Security 5.8 to address deprecations, then follow the official migration guide to upgrade to version 6.0 before moving to 7.0. [4, 7]

Notice 🤖: This content was generated using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

---

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Uncontrolled Recursion SNYK-JAVA-COMNIMBUSDS-10691768	113	org.springframework.security:spring-security-oauth2-client: 5.7.8 -> 7.0.0 Major version upgrade Reachable Proof of Concept

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[bwappsec]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.