Upgrading from 3.1.1 to 4.1.2 causing the old token to not be valid anymore

[dehghanfar]

Question

I was wondering if the JWT Token that has been created by 3.1.1 will be still valid after upgrading to 4.1.2.

The reason I ask this question is, I want to know if my logged in users will be able to stay logged in and their Token will be refresh by my system to a new token or the Token that has been created by ID4 V 3.1.1 is not going to be valid after upgrading STS to 4.1.2

We upgraded our ID4 to 4.1.2 based on the code provided by Skoruba but after upgrading the logged in users all got logged out and they had to re-login. This happened in our Dev Env and looking to see if there is a way to prevent this when we want to go to Production.

The error we are getting is a 401 error (Invalid Token)