It sounds like you have two conflicting versions of a remember me manager in your applications?
They each format the cookie differently, and this causes the stock RememberMeManager to throw an exception. If this assumption _is_ correct Shiro should probably log and ignore this exception and NOT fail. Can you provide an example of your request/response headers that is causing this issue? (that should make it easy to write a test) On Tue, Jul 30, 2019 at 3:32 AM Francois Papon <[email protected]> wrote: > Ok, thanks for your feeback. > > We will take a look. > > regards, > > François > [email protected] > > Le 30/07/2019 à 09:08, jubax a écrit : > > Hi François, > > > > > > fpapon wrote > >> Hi, > >> > >> Can you try with the latest version 1.4.1 ? > >> > >> regards, > >> > >> François > >> fpapon@ > > > > With 1.4.1 I get the same behavior. > > > > Thanks, > > > > Jürgen > > > > > > > > -- > > Sent from: http://shiro-user.582556.n2.nabble.com/ >
