Issue Summary

Regenerating the OAth token with Github Enterprise setup from DVCS page might result in the below error. This error could be misleading at times if the configuration is not working even after multiple tries. If the repos are getting synced with after this operation then the OAth token has been generated successfully.

Steps to Reproduce

1. Login to GitHub Enterprise as a user with admin permissions on the account.
2. Navigate to Settings > Developer settings > OAuth apps.
3. Select your OAuth app.
4. On your app page, click Revoke all user tokens to remove all old user tokens for this application.
5. Click Generate a new client secret.
6. Copy the new client secret and then delete the old client secret.
7. Go to the DVCS accounts page in Jira.
8. Click the More options (•••) menu next to your existing GitHub Enterprise account or workspace.
9. Select Reset OAuth settings.
10. Paste the existing Client ID as Key and the new client secret as Secret to regenerate the access token.

Expected Results

DVCS should confirm that the Oath token has been generated successfully.

Actual Results

Workaround

• Verify if the Sync is working fine, then the setup has been configured perfectly.
• Contact support if you need any more clarification.