Ok, I think some of my problem is outside Shiro. I've gotten past most
of my issues (whether right way or wrong) and realized I was still
getting a cookie with the JSESSIONID set and I see some resources are
injecting a session scoped bean. I guess the container is starting up a
session outside of Shiro and that is sticking around. I'm working
through replacing those usages but the couple I've migrated appear to be
working correctly. I do have another question about
PrincipalCollection, but I'll start another thread if I feel like coming
back around.
Dave
On 10/29/2024 10:45 PM, le...@flowlogix.com wrote:
I am still unclear what’s happening.
What you are explaining should work fine, however something is clearly
not working for you.
Can you provide an http://www.sscce.org ?