Vscode-pull-request-github: 503 on vscode-auth.github.com when signing in to GitHub Enterprise

Created on 5 Nov 2018  路  12Comments  路  Source: microsoft/vscode-pull-request-github

  • Extension version: 0.2.3
  • VSCode Version: 1.27.2
  • OS: macOS 10.14.1

Steps to Reproduce:

  1. Open Code with a GitHub Enterprise repo open
  2. Click "sign in" on the extension pop-up
  3. Click green "Continue" button
  4. Wait for a while (60s?)
  5. See a Heroku 503 page (see below)

image

authentication bug

All 12 comments

I ran into the same issue. I tried to give a PAT as well, but the extension says invalid token.

I ran into the same issue. I tried to give a PAT as well, but the extension says invalid token.

I'm having the same issue. After I approve my account, it automatically takes me to 404 page. I click on the "signing in to github.(corp).com..." it asks for token. what token?

same here, I tried a personal access token but it didn't work. just keep saying it's an invalid token, keep showing the error page

@YeThor @rockypabillore That sounds like an issue fixed in the most recent release. What version of the extension are you using? If you update the extension, does it help?

I just tried with the last version and got the same issue.

0.3.0

Breaking Changes

From 0.3.0, you at least need VSCode 1.30 (including Insiders) to install and run the extension.

I've just tried this with VSCode 1.30 - The OAuth flow still failed with the same old application error as in the picture from above comments, but giving a PAT and server name allowed me to sign in.

@vinod386 how do you manually provide a token?

@romanlevin You could just click on the signing in.. field on the bottom left of VSCode, then provide the token and server at the top.

@vinod386 where did you get the token and what scope / permissions did you set?

@ProLoser You can follow the steps in this link to create your token - https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/

The scope set on my token is - read:user, repo, user:email, write:discussion

Was this page helpful?
0 / 5 - 0 ratings