make favicon public
Even though the resource doesn't exist, chrome (and probably other browsers) will request the favicon after requesting the "second-factor" page. Requests for the favicon prevented proceeding past the second-factor page and never hitting the POST to "second-factor". Instead, the sample prompts for the username, again. Exposing favicon (even though it doesn't exist) resolves the issue.
This commit is contained in:
parent
bc3fc6b2e0
commit
162ee60efb
|
@ -47,6 +47,7 @@ public class SecurityConfig {
|
||||||
// @formatter:off
|
// @formatter:off
|
||||||
http
|
http
|
||||||
.authorizeHttpRequests((authorize) -> authorize
|
.authorizeHttpRequests((authorize) -> authorize
|
||||||
|
.antMatchers("/favicon.ico").permitAll()
|
||||||
.mvcMatchers("/second-factor", "/third-factor").access(mfaAuthorizationManager)
|
.mvcMatchers("/second-factor", "/third-factor").access(mfaAuthorizationManager)
|
||||||
.anyRequest().authenticated()
|
.anyRequest().authenticated()
|
||||||
)
|
)
|
||||||
|
|
Loading…
Reference in New Issue