New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add X-GitHub-SSO to response-headers #663
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cheers :)
Awesome! Thanks you kindly, good sir (@gr2m). 👍 |
@armw4 I was reading the article you attached above.. What does the statement below actually means? I was trying to connect to my organization repository with sourcetree.. but I couldn't get it work.. Guess I might not whitelisting my repository correctly.. |
Hmm...it’s been a while since I dealt with this. I recall needling to interrogate the aforementioned response header inside my express.js app to determine if SSO was enabled for an organization. I believe I tenderer an error message of sorts to warn the user they needed to use a token which encapsulates the SSO authorization as opposed to Basic Auth. The token takes SSO into account and is more restrictive as opposed to all encompassing and permissive like Basic Auth (you have to explicitly grant org access, repository access, etc.). |
Yes! I found it. You need to use a Personal Access Token to access web resources when SSO is enabled. It allows the admin to track your access and tokens (great for Enterprise-Grade organizations). I encountered this while building an Atlassian Connect Express Jira Cloud add-on. |
@armw4 Thank you so much for responding so quick, and spending time on researching this |
Haha..no problem sir have a great 21st of October, 2019 ⭐️ 🌍 ☮️ |
No description provided.