-
Notifications
You must be signed in to change notification settings - Fork 5.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WebClient reusing inbound WebSecurity on outbound calls #10589
Comments
@lashower I suspect the issue is related to a misconfiguration. Take a look at this sample, which has a Resource Server that is configured as a Client as well. See the Controller method, which receives the If you're still having issues after looking at the sample, please provide a minimal reproducible sample so I can efficiently troubleshoot your issue. |
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed. |
First, Thank you so much for your help. I worked with 2 architects and they had no clue on how to fix this. |
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed. |
Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue. |
Spring Web Starter version: 2.4.12
Spring Web Version: 5.3.12
Issue:
My application implements both a oauth2 resource server and oauth2 client and both use different authentication methods, but I can only get one working at a given time.
My inbound Controllers are protected by a Microsoft ADFS Token which is configured in a WebSecurityConfigurerAdapter that includes a jwt token.
I make an outbound call to another application that uses Pivotal Cloud Foundry UAA service client. When I make the call to that application with a Controller that is protected by my WebSecurityConfigurerAdaptor, it fails with this exception:
I have found some outdated examples on how to tune my WebSecurityConfigurerAdapter (when not using jwt) to set a default principalName, but I think it is weird that my outbound calls are using configurations set up for my inbound calls.
Here is the WebClient code I am using
Is there a different class or tuning for my WebClient that will not reuse components of my inbound WebSecurity?
The text was updated successfully, but these errors were encountered: