Describe the bug When i custom reactiveUserDetail or custom reactiveAuthenProvider , maximumSessions() not working

**code @Bean SecurityWebFilterChain filterChain(ServerHttpSecurity http) { http // ... .sessionManagement((sessions) -> sessions .concurrentSessions((concurrency) -> concurrency .maximumSessions(SessionLimit.of(1)) ) ); return http.build(); }

Expected behavior I want a user only exist a session Sample

https://docs.spring.io/spring-security/reference/reactive/authentication/concurrent-sessions-control.html

Comment From: ngocnhan-tran1996

You can find a sample in the last section and check it with your config

https://docs.spring.io/spring-security/reference/reactive/authentication/concurrent-sessions-control.html

Comment From: jzheaux

Thanks for getting in touch! It feels like this is a question that would be better suited to Stack Overflow. We prefer to use GitHub issues only for bugs and enhancements. Feel free to update this issue with a link to the re-posted question (so that other people can find it) or add more detail if you feel this is a genuine bug.

Comment From: githubanhduong

thank you