Secure Token Error - Session not accepted

[Clinton_Reeder]

We have been working with SecureTokens for a while and we keep coming across an issue where if the securetoken that was generated contains an equal sign anywhere inside of the text, it doesn’t allow the connection. The connection works if you change the start and end times such that an equal sign isn’t generated so we have tracked it to down to that.

ie 8SVakfI=7EGKN0rxWW5UPvdVFY5v689n5l6IcCiI7yI= doesn’t work
In3Iv6LexlSX8Xob4Gk8FgA6adIDfeOaK6wyTejWsZ4= will work (incremented time by one second)

Do we just need to escape the equal sign in the middle of the token? To make it URL safe, the standard is to just drop the equal sign but that isn’t working either.

[marcosandrew]

Hi @Clinton_Reeder,

To resolve the Secure Token error due to the equal sign, you can use Base64 URL encoding. This involves replacing the equal sign (=) with a URL-safe character, such as hyphen (-) or underscore (_). This ensures that the SecureToken remains intact and can be safely used in your connections without encountering issues related to the equal sign.