Hello, Stuart.
First of all, thank you for your suggestion.
Second, sorry for my lack of feedback, I've being away from this task in the last days.
I did as you said, but I've had no success yet.
Setting changeSessionIdOnLogin to false, avoids the first attempt to create a new session, in CachedAuthenticatedSessionHandler class. But just after that, session will be created, and of course, with a new session id.
If I also set cacheable to false, when invoking authenticationComplete, so no session will be created at all. But somehow, the authentication mechanism enters in a loop even with my AuthenticationMechanism returning AUTHENTICATED.
It seems that I am unable to finish my authentication without an instance of HttpSession created, is this expected?
What else could I do?