Token key has changed in our dev env causing 401 errors #178
Replies: 1 comment
-
Hmm, restarting our Auth server solved the issue. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We have an issue in our dev environment that is blocking development. It does not occur in our prod environment.
In our dev environment with tenant id
391c8c4c-6a2a-40fd-ab98-226b6baa5155
we suddenly get 401 errors trying to open or create an item.The key used by the token changed overnight - it used to be:
but today it is
this key doesn't match any of the ones listed here so Authentication fails.
I don't think we changed anything to cause this. The error we get trying to authenticate is this:
Beta Was this translation helpful? Give feedback.
All reactions