- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
I found the issue, and I believe it's a bug with the hosted UI.
The Sign In page seems to rely on an XSRF-TOKEN
cookie . If you open up two hosted UI windows that are both on the "Sign In as..." screen, even if they have different "state" query variables, the cookie value for XSRF-TOKEN
for both windows will be the same. It appears that once you log in, that XSRF token becomes invalid. The hosted UI does not change this value, so if you try to login again on the second window, it will try to use the invalid token, fail, and redirect you to the /error
page. If you hit the back button (or refresh the page before logging in), it will re-generate the XSRF-TOKEN
and unblock the authentication problem. Hopefully this helps someone else facing this issue. I am unsure how I can report this as a bug, so if anyone could reach out to me with that info that would be awesome.
My app is facing a similar issue. Customers are stuck after they hit sign in if there was an existing tab already open? Has anyone else figured out a solution / workaround yet?
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa