• We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Hi,

      I am trying to connect Jira to our internal GitHub enterprise installation and I have come across an "issue", which is stopping me from proceeding.

      Our GitHub instance is setup to authenticate via LDAP and the DVCS connector requires GitHub to use OAuth authentication mode to validate the account.

      We can't switch the authentication mechanism in GitHub because it will break the tool for the rest of the company.

      Please advise.

      Regards,

      Oliver

            [JSWSERVER-14535] Linking Jira with Github Enterprise

            Problem solved.

            Jira was running behind a proxy and the Github domain was not in the ignore list.

            Oliver Pereira added a comment - Problem solved. Jira was running behind a proxy and the Github domain was not in the ignore list.

            ZehuaA added a comment -

            Could you try to reset the OAuth token on the DVCS Accounts page? Or delete the account on the DVCS Accounts page and recreate it. Make sure that you use the GitHub Enterprise account that has admin access to login and grant access when recreating the DVCS Account.

            ZehuaA added a comment - Could you try to reset the OAuth token on the DVCS Accounts page? Or delete the account on the DVCS Accounts page and recreate it. Make sure that you use the GitHub Enterprise account that has admin access to login and grant access when recreating the DVCS Account.

            I have made the account as a admin (owner) on one of our repositories in GitHub but I am still getting this error.

            2014-03-31 16:31:46,694 http-bio-8080-exec-3 ERROR Oliver.Pereira 991x362x1 1m16z4z 192.168.56.1 /rest/bitbucket/1.0/organization/6/syncRepoList [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service
            com.atlassian.jira.plugins.dvcs.exception.SourceControlException: Error retrieving list of repositories
                    at com.atlassian.jira.plugins.dvcs.spi.github.GithubCommunicator.getRepositories(GithubCommunicator.java:153)
            

            Oliver Pereira added a comment - I have made the account as a admin (owner) on one of our repositories in GitHub but I am still getting this error. 2014-03-31 16:31:46,694 http-bio-8080-exec-3 ERROR Oliver.Pereira 991x362x1 1m16z4z 192.168.56.1 / rest /bitbucket/1.0/organization/6/syncRepoList [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service com.atlassian.jira.plugins.dvcs.exception.SourceControlException: Error retrieving list of repositories at com.atlassian.jira.plugins.dvcs.spi.github.GithubCommunicator.getRepositories(GithubCommunicator.java:153)

            Hi,

            I managed to sort out the authentication issue but I have stumbled upon another "issue" and trying to find a way around it (if there is any)

            We currently have a lot of private repositories and due to various reasons they cannot be made public. But we would like to be able to display the development information against the corresponding Jira ticket in Jira

            Current the Github account we use to setup the DVCS does NOT have permissions to view the repositories in GitHub but it will be resolved in due course.

            But I am not sure how this can be achieved.

            Oliver Pereira added a comment - Hi, I managed to sort out the authentication issue but I have stumbled upon another "issue" and trying to find a way around it (if there is any) We currently have a lot of private repositories and due to various reasons they cannot be made public. But we would like to be able to display the development information against the corresponding Jira ticket in Jira Current the Github account we use to setup the DVCS does NOT have permissions to view the repositories in GitHub but it will be resolved in due course. But I am not sure how this can be achieved.

            ZehuaA added a comment -

            Hi oliver.pereira2,

            The OAuth required to connect DVCS Connector to GitHub is not the "OAuth Authentication" that you are thinking about. DVCS Connector only requires you to generate OAuth key/secret from the Applications settings. You could still use LDAP for your usual user authentication.

            Please take a look at the section "GitHub and GitHub Enterprise" in Step 1 of https://confluence.atlassian.com/display/BITBUCKET/Linking+Bitbucket+and+GitHub+accounts+to+JIRA .

            Let us know if you still have problems establishing the linking.

            Regards,
            Zehua

            ZehuaA added a comment - Hi oliver.pereira2 , The OAuth required to connect DVCS Connector to GitHub is not the "OAuth Authentication" that you are thinking about. DVCS Connector only requires you to generate OAuth key/secret from the Applications settings. You could still use LDAP for your usual user authentication. Please take a look at the section "GitHub and GitHub Enterprise" in Step 1 of https://confluence.atlassian.com/display/BITBUCKET/Linking+Bitbucket+and+GitHub+accounts+to+JIRA . Let us know if you still have problems establishing the linking. Regards, Zehua

              Unassigned Unassigned
              f4e9b6ad0071 Oliver Pereira
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: