Skip to content

Using WebSecurityConfigurerAdapter breaks the app services #6

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

Open
BenDol opened this issue Sep 11, 2018 · 0 comments
Open

Using WebSecurityConfigurerAdapter breaks the app services #6

BenDol opened this issue Sep 11, 2018 · 0 comments

Comments

@BenDol
Copy link

BenDol commented Sep 11, 2018

When attempting to migrate this sample to my own environment I've run into an issue where as soon as I include a WebSecurityConfigurerAdapter in the app, the test no longer works and I receive a 401 error. This is because the app no longer authenticates strictly from the OAuth2AuthenticationManager it seems to skip this entirely for what ever reason.

Would you be able to help me understand how I can resolve this issue? Obviously the filter or process is being short circuited, but I haven't had any luck figuring out why.

How to reproduce:
Add the following anywhere in one of the apps (account/customer):

import org.springframework.context.annotation.Configuration;
import org.springframework.security.config.annotation.web.configuration.WebSecurityConfigurerAdapter;

@Configuration
public class SecurityConfig extends WebSecurityConfigurerAdapter {


}

Then start the services and attempt to run the test.

I need to be able to authenticate my application both using EnableOAuth2Client or EnableOAuth2Sso as well as the way you are utilizing it. Perhaps someone could sample how this would work next?

Any help is much appreciated, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant