SessionExpiredException thrown but no relogin performed about bco.authentication HOT 3 CLOSED

This does not solve the issue, but either the component with that ticket is running for a lot longer than 3 - 5 days or the authenticator is distributing outdated tickets. A validity period of [31.1.2020 - 21:11:36:55] - [7.2.2020 - 21:15:36:55] means that this ticket was generated on the 31st of January. So, in order for this to happen the component should have been running since then. Furthermore, the component has not performed any action since then (because every action should update the ticket) or, which is more likely to cause such a bug, somehow the session manager exchanged an up-to-date ticket for an outdated one.

from bco.authentication.

So, in order for this to happen the component should have been running since then.

Yes, you are right, possibly openhab and therefore the bco-eclipse-smarthome binding was running since 31st of January. But BCO was restarted at least a couple of times since then.

Furthermore, the component has not performed any action since then (because every action should update the ticket)

Is this actually possible in a live system? I mean any MotionSensor state update is triggering a requestDataAuthenticated that then updates the ticket, right?

somehow the session manager exchanged an up-to-date ticket for an outdated one.

But even then, we have two different bugs because no relogin is performed, right?

from bco.authentication.

Should be fixed by commit 08f7872. Most likely a remote instance remained running while BCO was restarted. Then an old ticket is used for the first requests. The problem was that the SessionManager did not timeout on some requests. Therefore, the re-login failed because of a deadlock.

from bco.authentication.