- Newest
- Most votes
- Most comments
Hi, based on your report that SSO login functions correctly in Safari but encounters issues in Firefox, the problem likely stems from a Firefox configuration or an extension. Please follow these steps:
- Disable each Firefox extension individually to identify the problematic one.
- If the issue persists with all extensions disabled, proceed with the following additional steps:
- Clear Cache and Cookies in Firefox: Sometimes corrupted cache or cookies can cause login issues. Go to Firefox settings, clear your recent history, and remove cookies.
- Disable ALL Firefox Add-ons: Some browser add-ons can interfere with web applications. Try disabling add-ons, especially those related to security or privacy, and attempt to log in again.
- Update Firefox: Ensure you are using the latest version of Firefox. Updates often include fixes for compatibility and security issues.
- Check Security Settings: Review your Firefox security settings. High security or privacy settings might block certain web functionalities needed for AWS SSO.
- Try Private Browsing: Use Firefox’s private browsing mode to see if the issue persists. This mode uses default settings and disables most add-ons, which can help identify if the problem is related to browser configuration.
Hope this address your issue, best regards. Lechu.
I'm on the latest version of Firefox. With or without extensions the issue happened. The problem did (see below) occur when using Private Browsing. The problem was occuring on multiple machines, always from Firefox. Different organisations too - meaning the AWS web application, and browser was the common factor.
Having made no changes, no browser updates, no extension changes - something has changed as I am no longer able to re-create the issue. I notice there is no longer a POST
into the whoAmI
endpoint. That's not a change from my browser, so presumably AWS have made some changes?
Obviously it is good that this issue has (at least for now?) been resolved Lechu. I cannot accept your answer though, I do not believe anything on my side has made this problem go away, and your answer puts all the onus on my client browser.
Relevant content
- asked 2 years ago
- asked 3 years ago
- asked 3 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 5 months ago
Thanks for sharing it with us.