error in wasp log - Failure to decrypt sid ; javax.crypto.BadPaddingException ; Invalid sid

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

What does the following error mean in the wasp logs?

 

Sep 07 08:30:50:984 DEBUG [https-jsse-nio-7443-exec-12, com.firehunter.ump.auth.JWTVerificationFilter] Recieved request from: 0:0:0:0:0:0:0:1
Sep 07 08:30:50:984 DEBUG [https-jsse-nio-7443-exec-12, com.firehunter.ump.auth.JWTVerificationFilter] Recieved request /dashboard/api/data/####### from: 0:0:0:0:0:0:0:1 token:<example>

Sep 07 08:30:51:283 DEBUG [https-jsse-nio-7443-exec-12, com.firehunter.ump.utils.SecurityUtil] Failure to decrypt sidjavax.crypto.BadPaddingException: Given final block not properly padded. Such issues can arise if a bad key is used during decryption.
Sep 07 08:30:51:283 DEBUG [https-jsse-nio-7443-exec-12, com.firehunter.ump.utils.SecurityUtil] Invalid sid <example>

 

Environment

Release : 20.4

Resolution

This error occurs after restarting wasp if someone has a Dashboard Designer dashboard open at the time of restart.  After the restart, the dashboard will try to refresh, but the restart will have invalidated the session, so the user will be presented with a login screen at the same time this error occurs.  It is ultimately benign.