Sounds great - it will help a lot! I would wait for 2.0.1 then! 🙂 ________________________________ From: lenny Sent: Friday, April 19, 2024 20:43
You are right! What you did is absolutely fine and supported. I forgot you can simply override SecurityManager instance in shiro.ini. Since you did it that way, everything should work correctly in 2.0 The realmAccessor solution should be the only thing you need. When 2.0.1 is released, ShiroFilter.unwrapSecurityManager() should be exposed as public method.
