Cascading command link does not keep token refreshed when idle

[Adam Elliott]

I am using a cascading link to send EMBEDDED_BINARY commands to a server with authentication enabled. It initially connects fine and commands can be sent successfully. If no commands are sent for a period of time though, the next command will fail with a org.yamcs.client.UnauthorizedException.

Is this a known issue? I feel the link should either keep the connection active, or at least re-authenticate if the original connection was idle too long.

 - Adam

[Adam Elliott]

This issue was fixed in version 5.13.3