-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
-
1.0
If a user saves a Github personal access token in the creation flow and then re-enters after the token has been revoked, they should receive in appropriate error message.
Repro Steps
- Navigate to /create-pipeline
- Select "Github"
- Enter a valid Github access token
- Navigate to Github and revoke the access token
- Navigate to /create-pipeline again
- Select "Github"
Expected Behavior
User should be prompted to enter a new access token. Ideally the user should get some feedback that it appears the credential is invalid.
Actual Behavior
"Loading" message displays forever. http://localhost:8080/jenkins/blue/rest/organizations/jenkins/scm/github/organizations/?credentialId=github 500 (Server Error)
{ "message" : "Server returned HTTP response code: 401, message: 'Unauthorized' for URL: https://api.github.com/user", "code" : 500, "errors" : [ ] }
- is blocked by
-
JENKINS-41439 Github /organizations API returns 500 when using credentialId tied to revoked Github personal access token
- Closed