security-oauth2 | Spring security OAuth2 | OAuth library

I'll try to provide an answer to the sequence of questions/challenges you're facing.

Based on comments and updates to the question, it looks like you have a few incorrect configurations to address. From our first round of comments:

• It looks like you've configured a confidential client (with a client secret, client authentication method, requireProofKey(true) not set

Note: Also, make sure you're browsing your application from http://127.0.0.1:4200, not http://localhost:4200.

From the update you provided in the question:

• You don't want to comment out config.setAllowCredentials(true); in your cors config as the browser needs to be able to send the JSESSIONID cookie with the silent renew process.
• Spring Authorization Server doesn't currently support refresh tokens for public clients, so my sample doesn't include that option useRefreshToken: true.
• Your .authorizeRequests() DSL usage is not correct. You don't want to have multiple invocations of that method, as the 2nd one overwrites the first one. You are also targeting the wrong endpoints in the default filter chain. It should look like the sample:

You could create custom filter that will be applied to all requests. Here is an example when user is a part of the jwt token.

I also face the same issue while migrating from springboot 2.3.8.RELEASE to 2.4.13 and I fixed it using

Here's the workaround that seems to work :

declare a threadExecutor :

Hello i did it this way, 1-find the .yo-rc.json file of you project 2-open the file and find the tag "authenticationType", it should appear like "authenticationType": "jwt", change it to "authenticationType": "oauth2" 3 - run again the jhipster command in your project.

Here you have a video: https://www.youtube.com/watch?v=YIRjgd_3sMQ

It's working now. I added a reverse-proxy and changed the ports of the provider urls to the internal docker port.

If you are using Spring Boot you should choose org.springframework.boot:spring-boot-starter-oauth2-client.
This includes Spring Security's OAuth 2.0 Client support and provides Spring Boot auto-configuration to set up OAuth2/Open ID Connect clients.
You can read about how to configure client in the Spring Boot reference documentation.
You can also find additional details in the Spring Security reference documentation.

If you are not using Spring Boot then you should choose org.springframework.security:spring-security-oauth2-client. This also provides Spring Security's latest OAuth 2.0 Client support, but does not include the Spring Boot auto-configuration.
The corresponding documentation is also the Spring Security reference documentation.

The third dependency you mentioned org.springframework.security.oauth:spring-security-oauth2 should not be used because it is part of the legacy Spring Security OAuth project, which is now deprecated.
The functionality that this library provided has now been moved into Spring Security.
That is what the Migration Guide describes, the migration from the legacy project to the latest Spring Security support.

You should not use the org.springframework.cloud:spring-cloud-starter-oauth2 at this time, because it relies on the legacy OAuth support.
This is likely to change in the future, as the Spring Cloud team updates to the latest Spring Security support.

After trying out different solutions this was how I was able to solve it.

I changed my OAuth2AuthorizationService bean to look like this.

The problem was occurring because the default authentication manager wasn't working for me, I had to implement one specifically for my problem.