Public issue shows "Unable to load page" when my SAML SSO session has lapsed #210118
Replies: 2 comments
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
|
Same issue here on AndroidTV. What the hell is wrong with this website? GitHub has deviated so god damned far from what it was in the beginning, it's unreliable garbage now that doesn't even spit out proper error codes or further information Unable to load page. What a piece of absolute crap. |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Issues
Body
A public issue shows "Unable to load page. Please reload page and try again" when I open it signed in. Reloading does not help. Signed out, the same URL renders fine.
The issue is cross-referenced from a private repository in an organization that enforces SAML SSO, and I had no active SAML session for that organization.
Steps to reproduce
Expected
The issue renders, without the timeline entry that needs SSO.
Actual
The page data comes back with
"issue": nulland this error, and the issue area shows the generic message:{ "type": "SAML", "message": "saml error", "path": ["repository", "issue", "timelineItems", "totalCount"] }Example: cloudnative-pg/cloudnative-pg#11126
Workaround
Start a SAML session for the organization and reload, or open the issue signed out.
The workaround section still assumes the SSO sign-in fixed the page for you; drop it if it didn't.
Guidelines
All reactions