Classic token SSO auth leaking between different orgs #146936
Replies: 1 comment
-
💬 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. ⭐ |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Bug
Body
Noticed a strange behaviour for the https://api.github.com/orgs/{org}/repos endpoint.
I have 2 orgs that need SSO authorization, OrgA and OrgB.
If my classic token has SSO enabled for OrgA, I am still able to get repos of OrgB as well.
If SSO is not enabled for either, I get a SAML error.
This does not seem like intended behaviour, can you confirm if this is a bug ?
Beta Was this translation helpful? Give feedback.
All reactions