Enhance error reporting when organization use SAML SSO
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 339
- Forks
- 93
- PR merge metrics
- No merged PRs in 30d
Description
Currently, we log that and just report a generic auth failure.
authentification failure, will retry another token: remote: The `xxxxx' organization has enabled or enforced SAML SSO. To access
remote: this repository, you must re-authorize the GitHub App `Mergify`.
fatal: unable to access 'https://github.com/xxxx/xxxx/': The requested URL returned error: 403
I have no idea how the github SAML SSO works, but I'm sure we can do better to make them aware they have to do something on their side to make rebase and backport working.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the logging path that turns the GitHub SAML SSO response into a generic authentication failure, then reproduce it with the quoted 403 output. Done means users are told that the organization requires SAML SSO reauthorization and what action is needed to make rebase and backport work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- authentication, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100