96
edits
GitHub/GHE SAML User FAQ: Difference between revisions
Jump to navigation
Jump to search
→Circle CI: webhooks error fixing
Cknowles-moz (talk | contribs) (more attempts to clarify that this is around troubleshooting and such rather than NEW access.) |
Cknowles-moz (talk | contribs) (→Circle CI: webhooks error fixing) |
||
| Line 110: | Line 110: | ||
While the above have worked for most, the following is direction from CircleCI on changes post SSO/SAML. (Note that updating PAT/SSH keys is also mentioned here, if you've done that from above, you won't need to here.) | While the above have worked for most, the following is direction from CircleCI on changes post SSO/SAML. (Note that updating PAT/SSH keys is also mentioned here, if you've done that from above, you won't need to here.) | ||
* [https://support.circleci.com/hc/en-us/articles/360043002793-Troubleshooting-CircleCI-access-after-enabling-Github-SSO CircleCI access after enabling Github SSO] | * [https://support.circleci.com/hc/en-us/articles/360043002793-Troubleshooting-CircleCI-access-after-enabling-Github-SSO CircleCI access after enabling Github SSO] | ||
===== CircleCI webhooks failing after SAMLing ===== | |||
After doing all of the above you should have error free access to CircleCI, but some reports have come in about intermittent webhooks failing with status code 400 | |||
* Have a SAMLd user re-issue the deploy key used in the affected repo. | |||
== Getting Help == | == Getting Help == | ||