Hmm wait, just realized a part of my yesterday fix was not pushed, will be done in few minutes if JL is ok
Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-05-23 9:22 GMT+02:00 Romain Manni-Bucau <[email protected]>: > Hi > > looked quickly and you should try logging out instead of invalidating the > session. > > BTW between two browsers I have no issue. Only in a single one with this > false logout (I'll check later if the issue is deeper but dont have time > right now). > > > > Romain Manni-Bucau > Twitter: @rmannibucau > Blog: http://rmannibucau.wordpress.com/ > LinkedIn: http://fr.linkedin.com/in/rmannibucau > Github: https://github.com/rmannibucau > > > 2014-05-22 22:23 GMT+02:00 hwaastad <[email protected]>: > > Hi, >> Pushed another version where you can log out on the secure page >> Still the same tomee principal name being used on the "unsecure". >> >> And, not quite following you. Two separate browser should generate >> different >> sessions? >> >> The: LogReceiver Standard: Caller Principal is correct but asynch methods >> is >> not. >> >> br hw >> >> >> >> -- >> View this message in context: >> http://openejb.979440.n4.nabble.com/Asynchronous-principal-propagation-tp4669547p4669571.html >> Sent from the OpenEJB User mailing list archive at Nabble.com. >> > >
