Skip to main content
cadbase
cadbase
Known Participant
November 3, 2022
Answered

Git Authentication

  • November 3, 2022
  • 2 replies
  • 528 views

I've been using Azure DevOps for RH2020 projects for a while now and would like to use GIT.

I have never been able to get RH Collaboration to work correctly from inside our corporate network. It only works when I work from home. The workaround was to use Visual Studio to handle the version control of the RH project folder.

I'm now switching from DevOps to GIT, but I have the same problem connecting to GitHub as I did with DevOps. I can connect from my home PC but not the work PC.

I have installed GIT on both machines, and on the work PC, I can successfully use git bash to clone a repository. To get that to work, I had set the forward proxy with git config --global https.proxy https://<proxy>:8080. That triggered a pop-up prompting for username, password and 2FA code, etc.

I created a RoboHelp Connection profile using https://github.<account>/<project>.git and supplied the same username, but RH times out when trying to clone the repo. Logging into GIT from Chrome or Edge first makes no difference.

I tried switching from HTTPS to SSH without success. Enter the SSH Private Key triggers the error:

"SSH Key could not be added to the. ssh=agent. Make sure that ssh-agent is running and the key is valid".

One link on the community suggests testing SSH connectivity first with ssh -T git@guthub, but that test fails on the corporate PC (so I'm guessing that Port 20 may be closed in the enterprise proxy or firewall).

The fact that git bash works with HTTPS on the enterprise PC suggests getting HTTPS to work from RoboHelp may be possible. RH2022 is failing to authenticate, or RoboHelp isn't using the same proxy server as git.

My only workaround would be to use the git command line for all source control commit, push and pull functions when working on the office PC and use RH Collaboration only on the home PC (where authentication is successful).

Are there any proxy settings in RoboHelp?

Can I set the authentication method for HTTPS connections to GIT?

      This topic has been closed for replies.
      Correct answer PWC - CADbase

      I tried using a Git repo at azure devops instead of GitHub and I'm able to push from git bash which prompts for credentials on first use through the Git Credentials Manager for Windows add-on for git. When I try to access that repo from inside Robohelp, I get the following message:

       

       

       


      I've found a solution finally; RH Collaboration now works from both the work PC and the home PC.

       

      The solution was to choose Other from the Git Server Provider and not Azure Repos and make sure Git Credentials Manager is installed (which is the default when installing Git for Windows).

       

      Making sure there's no .git folder present in the test project folder, open the project in RH2022 and user Add Project > Connection. A pop-up from Git Credentials Manager then prompts for a password to the internal forward proxy in the enteprise network:

       

      I entered the indernal domain password for by current Windows user. 

      A scond pup-up from Git Credentials Manager then prompts for a password for the DevOps repo.

       

       

      This password is not the login used to connect to Azure DevOps but it's the password you generate in the DevOps portal for the Git repository.

      After entering that password, the project is uploaded and all subsequent edits made inside RH2022 can be committed and pushed to the remote repo using the menus.

       

      2 replies

      cadbase
      cadbaseAuthor
      Known Participant
      November 3, 2022

      Just an update ... the posting at https://community.adobe.com/t5/robohelp-discussions/git-devops-repo-quot-unable-to-push-fatal-authentication-failed-quot/m-p/11442612#M133140 is similar and in 12 says "The first time you open/connect to the profile, RoboHelp will prompt you to enter the password.". That prompting isn't happening on the work PC. Tried creating a new connection profile but no joy.

      Jeff_Coatsworth
      Community Expert
      Jeff_CoatsworthCommunity Expert
      Community Expert
      November 3, 2022

      All this certainly sounds like you have an issue with the way your work environment is configured - your best bet is to work with the RH folks using the tcssup@adobe.com address to be able to see what's blocking you at work.

      P
      PWC - CADbase
      Inspiring
      November 3, 2022

      I tried using a Git repo at azure devops instead of GitHub and I'm able to push from git bash which prompts for credentials on first use through the Git Credentials Manager for Windows add-on for git. When I try to access that repo from inside Robohelp, I get the following message:

       

       

       

      A
      Community Expert
      AmebrCommunity Expert
      Community Expert
      November 3, 2022

      I assume you've worked through all the documentation here, including all the notes?
      https://helpx.adobe.com/robohelp/using/git.html

       

      From a quick scan by a noob, there's a note about an environment variable clash, a sentence about checking firewalls and a couple of notes about SSH  which seem like good places to double or triple check.

       

      If no-one else pops up with suggestions, then I think you need to contact support. The email address is recommended as it goes to a dedicated RoboHelp team. https://helpx.adobe.com/contact/enterprise-support.other.html#robohelp

      P
      PWC - CADbase
      Inspiring
      November 3, 2022

      Yes I've followed those notes.

       

      The fact that ssh -T git@guthub.com fails to connect from the command line proves the SSH port isn't open and therefore I won't be able to SSH on the work PC (either inside RH or from git command line), but I'm hoping to be able to use HTTPS in RoboHelp because that does work fine from the git command line as 443 is open. 

       

      On the home PC, RH prompted for the git password and 2FA code, so presumably it was uing OAUTH2 to get a token. Our browser is controlled in the Enterprise environment and policies there may be preventing the OAUTH2 process from completing.

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices