Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-14217

Error obtaining access token while configuring Github integration

XMLWordPrintable

      The problem:

      While configuring Github integration, the setup screen returns "error obtain access token" as in the following screenshots:

      The following appears on atlassian-jira.log:

      2014-04-08 10:32:45,944 http-bio-8622-exec-15 WARN admin 632x331x1 1ycok0n 192.168.10.136 /secure/admin/AddGithubOrganization!finish.jspa [spi.github.webwork.AddGithubOrganization] Error obtaining access token. Cannot access https://github.com from Jira.
2014-04-08 10:32:45,944 http-bio-8622-exec-15 WARN admin 632x331x1 1ycok0n 192.168.10.136 /secure/admin/AddGithubOrganization!finish.jspa [spi.github.webwork.AddGithubOrganization] Caused by: https://github.com/login/oauth/access_token

      Current behavior:

      If you click "Try Again" it redirects you to Github 404 page. If you click "Cancel" you see that the integration is set, but not all repositories appear on the list.

      The only way to get the full repositories list is by selecting "Refresh list" as in the screenshot bellow:

      Expected behavior:

      The setup screen should complete the operation without any error and the list of repositories should be display without the need to select "Refresh list".

        1. DVCS_1.png
          DVCS_1.png
          41 kB
        2. DVCS_2.png
          DVCS_2.png
          28 kB
        3. DVCS_3.png
          DVCS_3.png
          12 kB

            [JSWSERVER-14217] Error obtaining access token while configuring Github integration

            Joshua Issac added a comment -

            I got this error when I was using the GitHub-hosted (non-on-prem) version of GitHub Enterprise. I had picked the 'GitHub' option in the dropdown instead of 'GitHub Enterprise'. I was able to work around the issue by picking 'GitHub Enterprise' instead of 'GitHub', and using https://github.com/ as the instance URL.

            Joshua Issac added a comment - I got this error when I was using the GitHub-hosted (non-on-prem) version of GitHub Enterprise. I had picked the 'GitHub' option in the dropdown instead of 'GitHub Enterprise'. I was able to work around the issue by picking 'GitHub Enterprise' instead of 'GitHub', and using https://github.com/ as the instance URL.

            ABDESSAMAD JARIR added a comment -

            Hi Team , facing same issue for Jira in Cloud. any help please

            ABDESSAMAD JARIR added a comment - Hi Team , facing same issue for Jira in Cloud. any help please

            poolukunta reddy added a comment -

            Hi Team , facing same issue. any help please.

            poolukunta reddy added a comment - Hi Team , facing same issue. any help please.

            Vielbert Victorio added a comment -

            Same issue, i've tried to use OAuth 2.0 but i can't find it anywhere.

            Vielbert Victorio added a comment - Same issue, i've tried to use OAuth 2.0 but i can't find it anywhere.

            Madan Deshpande added a comment -

            I'm facing same issue with Server hosted GitLabs 

            Madan Deshpande added a comment - I'm facing same issue with Server hosted GitLabs 

            jamal added a comment - - edited

            We are having same issue:

             
            Error obtaining access token. Cannot access https://www.github.com from Jira.

            jamal added a comment - - edited We are having same issue:   Error obtaining access token. Cannot access https://www.github.com from Jira.

            Ivy Clark added a comment -

            Still no joy, trying to connect to Github Enterprise from Jira server 7.10.

            SSLPoke connected successfully, but Jira is still not happy and unable to connect. 

            Ivy Clark added a comment - Still no joy, trying to connect to Github Enterprise from Jira server 7.10. SSLPoke connected successfully, but Jira is still not happy and unable to connect. 
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2852208 ] New: JAC Bug Workflow v3 [ 2938190 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Symptom Severity Original: Minor [ 14432 ] New: Severity 3 - Minor [ 15832 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2546192 ] New: JAC Bug Workflow v2 [ 2852208 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]

              Unassigned Unassigned
              tcomasseto Tiago Comasseto
              Affected customers:
              0 This affects my team
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: