-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Document how to fix "Resource protected by organization SAML enforcement" #2661
Comments
Thankfully google took me here so this issue already acts as a FAQ entry. |
Bumping this as it fixed my problem 👍🏼 |
This was super helpful. Spent an unnecessary amount of time trying to "fix" this "issue". Thanks! |
Super helpful, fixed my issue immediately. |
Fixed my issue as well, thanks a ton! |
I have a service connection between Azure DevOps and GitHub for the pipelines to communicate with. It isn't possible to have the user re-authorize with a command. How do I fix the service connection to be re-authorized so when the pipeline is triggered it doesn't need this? |
Thanks for the solution. |
This is not fixed. Re-open please. |
for posterity, I'm explicitly linking this back to #5054 where the original solution was reworked to give users direction to authorize the organization associated with the PAT within the web browser: Lines 158 to 166 in 6f558c9
|
@zyrain : Please create a new issue including terminal commands, output, |
When an organization enables SAML enforcement,
gh
starts giving the following error:This is confusing, because if you check your https://github.com/settings/tokens page, the
gh
token is not there, so it's not immediately obvious what the user should do.What is required is re-authentication, but it would be a good idea to cover this in a FAQ entry:
Or maybe just tell the user to run
gh auth login
when the command fails with that error.The text was updated successfully, but these errors were encountered: