Browse Source
Previously if a user happened to provide an @EnableWebSecurity bean the SecurityProperties would not be created, which is fine until you add the Actuator (which needs them). Fixed by adding an explicit SecurityProperties @Bean if not already present.pull/165/head
2 changed files with 23 additions and 2 deletions
Loading…
Reference in new issue