Details
Description
UserSecurityAdvice is not being applied to UserManager because of a conflict of the advisorId in applicationContext-service.xml and with the bean id in security.xml. Both have an entry for "userManagerSecurity" The bean from security.xml seems to dominate and thus the UserSecurityAdvice is not applied. The current unit tests do not fail on this problem because the unit test is not configured with the same naming conflicts. Changing the name of the id in one or the other fixes this problem.
Activity
Matt Raible
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Fix Version/s | 1.9.4 [ 10090 ] | |
| Fix Version/s | 2.0 [ 10005 ] | |
| Affects Version/s | 1.9.4 [ 10090 ] |
Matt Raible
made changes -
| Component/s | Security [ 10006 ] |
Matt Raible
made changes -
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
Matt Raible
made changes -
Do you have a test case or scenario to prove that this happens?