I've posted about this in one of the other topics, but it's becoming a bigger and bigger issue. It needs its own post.
We have a created a web site for our company for internal use using Ignition 8.1. The whole site requires authentication, for which we use our Windows logins/passwords (ActiveDirectory, in other words). Users typically have browser bookmarks to go directly to their frequently-used pages.
Those bookmarks work . . . for a while. But after a few weeks, the users get odd behavior. The user follows the bookmark and authenticates as normal. But the authentication fails. The message on the screen says, "HTTP ERROR 400 Bad Request", followed by "/data/federate/callback/ignition/bridge" and a restatement of the error.
In the other post, the user was advised to turn on logging for Gateway.federationRoutes, which I have done as well, and I get the same message about "Unable to parse the error redirect URI from the relay state JWT" that they were getting.
Somehow, the browser bookmark (both Chrome and Edge so far) is key to the problem. When given a straight-up link to the page they want to go to, these users can follow it, authenticate, and arrive at the page. But following a browser bookmark to the exact same page and authenticating as part of that process triggers the issue.
This is increasingly becoming an annoyance as more and more users are making use of the site but then report to me that they "can't log in", when in fact they can, they just can't use the nice convenient browser bookmarks they set up.
My best guess is that browsing to the site via a bookmark must carry with it some additional information (a cookie? Something similar?) that coming in via a simple link does not, and that additional information must be expiring after some length of time and triggering a login failure. Is anyone else seeing this, and does anyone have any ideas for a proper solution? Telling people not to use bookmarks isn't cutting it.