Private contributions to organization with SSO hidden from authenticated users without active SSO session

[mattolson]

Select Topic Area

Bug

Body

Description

When a user enables "Private contributions" on their profile and is a member of an organization that uses SAML SSO, there's an inconsistency in how those contributions are displayed to different viewers.

Steps to reproduce

1. User A enables "Private contributions" in their profile settings
2. User A is a member of Organization X, which requires SAML SSO
3. User A makes commits to private repos in Organization X
4. User A views the contribution graph on their own profile while not authenticated to Organization X

Actual behavior

• Viewer who is not logged in: sees User A's contribution graph including anonymized contributions from Organization X
• User A who is logged in but does not have an active SSO session with Organization X: does not see contributions from Organization X on User A's profile

Expected behavior

These two viewers should see the same thing. An unauthenticated viewer should not have more visibility into a user's contributions than an authenticated viewer.

Why this matters

• The current behavior is counterintuitive and confusing
• It undermines the privacy model since logging out reveals more information than being logged in

Environment

• Observed on github.com (not Enterprise Server)

[github-actions[bot]]

💬 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 ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

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. ⭐

[mecodeatlas]

Hi @mattolson, thanks for the detailed report.

We’ve shared this with the responsible team internally, and it’s now tracked on their backlog.
While we can’t guarantee an immediate fix, the team is aware and will follow up as they’re able.

Thanks for flagging this!

[samrathreddy]

Hi @mecodeatlas, is there any update?