You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm configuring Spring Session integration with Spring Security on concurrent session control, on Spring Boot. I followed the steps illustrated on Spring Session reference but got an error:
Description:
Field sessionRepository in com.xxx.configuration.WebSecurityConfiguration required a bean of type 'org.springframework.session.FindByIndexNameSessionRepository' that could not be found.
The injection point has the following annotations:
I wonder if I should define a bean of type 'FindByIndexNameSessionRepository' somewhere in my configuration, even with Spring Boot's auto-configuration? I looked up documents of Spring Session, Spring Boot and Spring Security but found no further information.
Is there any mistake in my usage of Spring Session (and Spring Boot's auto-configuration) or the document needs further explanation of this integration ( or it is a bug ) ?
The text was updated successfully, but these errors were encountered:
I'm configuring Spring Session integration with Spring Security on concurrent session control, on Spring Boot. I followed the steps illustrated on Spring Session reference but got an error:
Versions:
Spring Boot 2.1.2.RELEASE
Spring Session 2.1.3.RELEASE
Spring Security 5.1.3.RELEASE
Here is some code for reproducing:
WebSecurityConfiguration.java:
application.properties:
I've also tried the code following, but it does not working:
WebSecurityConfiguration.java:
I wonder if I should define a bean of type 'FindByIndexNameSessionRepository' somewhere in my configuration, even with Spring Boot's auto-configuration? I looked up documents of Spring Session, Spring Boot and Spring Security but found no further information.
Is there any mistake in my usage of Spring Session (and Spring Boot's auto-configuration) or the document needs further explanation of this integration ( or it is a bug ) ?
The text was updated successfully, but these errors were encountered: