SEC-1593: Custom BeanPostProcessor are not applied for beans referenced by security infrastructure #1832

Closed
spring-issuemaster opened this Issue Oct 18, 2010 · 4 comments

1 participant

@spring-issuemaster

Michal Dvorak (Migrated from SEC-1593) said:

While it works fine in 3.0.3, with 3.1.0.M1, all beans referenced by security namespace are initialized before custom BeanPostProcessor are run. Tested on provider and entrypoint, but i assume its general problem.

@spring-issuemaster

Michal Dvorak said:

In short my config was
security:debug/




/security:authentication-manager





/security:http


....

@spring-issuemaster

Luke Taylor said:

Sorry, but I can't reproduce this. Both my custom AuthenticationEntryPoint and AuthenticationProvider are successfully post-processed in testing.

Could you provide a test case which reproduces the issue?

@spring-issuemaster

Michal Dvorak said:

hmm, i failed to reproduce it on dummy project too. It may be some combination of libraries i use - it still happens on "full project". When i hit the time i'll need to upgrade spring security, i will investigate it further, and possibly ask to reopen this.

Thank you for your efforts, i'm just trying to make this great library better ;)

@spring-issuemaster

Luke Taylor said:

Thanks for the update. Let us know what you come up with. In the meantime, I'll keep a lookout for over-eager initialization issues.

@spring-issuemaster spring-issuemaster added this to the 3.1.0.M2 milestone Feb 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment