1. Balu Krishnasamy
  2. Beta Testing
  3. Tuesday, 24 March 2020 02:38 AM UTC

Environment: PB 2019 R2 Beta; Git; Github account with SSO enabled.

Hello - I get this Login error,
"Failed to perform the specified operation. Please make sure you can connect to the server repo"
while i am trying to connect to a workspace on Github.
My company has made SSO mandatory so can't move away from that. If this doesn't work with Appeon, then may be we wont be able to use the cool new git features at all and will be stuck with VSS (yep, that's right).

BTW, my ssh key is SSO enabled and this all works great with tortoise git outside Appeon. Any thoughts on the issue?

Thanks
Balu

Accepted Answer
Tom Jiang @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 24 March 2020 12:39 PM UTC
  2. Beta Testing
  3. # Permalink

Balu,

You can try using a PTA as both the user name and password in PB IDE to access your repository on GitHub. 

To create a PTA, you can click on your icon on the upper-right corner on GitHub > Settings > Developer Settings > Personal access tokens ...

Regards,

Tom Jiang

Comment
There are no comments made yet.
Balu Krishnasamy Accepted Answer Pending Moderation
  1. Tuesday, 24 March 2020 15:32 PM UTC
  2. Beta Testing
  3. # 1

@Tom Jiang, Thank you! I was just going to send you it didn't work BUT i enabled SSO on the PAT and voila, it worked! Thanks again for your suggestion!

~B

Comment
  1. ASHWINI MISHRA
  2. Monday, 10 January 2022 17:34 PM UTC
Thanks for the response but I am still getting same error.

---------------------------

Login

---------------------------

Failed to perform the specified operation. Please make sure you can connect to the server repository.

---------------------------

OK

---------------------------



Source Control System: Git

Repository URL: HTTPS link of GitHub folder in which source control and .PBW file resides

Workspace file: abcd.pbw

Authentication type: Token

User Id: PAT

Personal Access Token: PAT
  1. Helpful
  1. Armeen Mazda @Appeon
  2. Monday, 10 January 2022 19:07 PM UTC
Please open a support ticket so we can investigate.
  1. Helpful
  1. Miguel Leeuwe
  2. Wednesday, 19 January 2022 09:38 AM UTC
Something similar happened to me some time ago. I had a PAT which was set to never expire but it still stopped working. Doing a "regenerate" fixed it.
  1. Helpful 1
There are no comments made yet.
Balu Krishnasamy Accepted Answer Pending Moderation
  1. Wednesday, 5 January 2022 13:19 PM UTC
  2. Beta Testing
  3. # 2

@Ashwini Mishra, see if you can connect to the GIT server outside powerbuilder like tortoise or other tool. This will prove you dont have any issues with your token/keys. Then try it in PB. I also believe Miguel Leeuwe is correct. Gosh! Its been a while and we haven't had any chance to connect to GIT after my initial research. Hopefully sometime this year!

Comment
  1. Balu Krishnasamy
  2. Tuesday, 18 January 2022 18:54 PM UTC
I happened to test this while i was working for another research and the SSO enabled PAT works for me. However, i get an error while trying to push which ill take a stab at some point but testing the connection seems to not be a problem.



Here are the detailed steps,

Created a folder with just pbls, pbw & pbt. Hooked the wkspc to GIT (created a local repo).

On the github.com, created a new repository and used this repo url inside PB(when you click Git Push the first time on the wkspc).

Created a new PAT in github.com (how to steps are provided by Tom Jiang above).

Applied SSO on this PAT(PAT pretty much has all the access selected/checked)

Copied & Pasted the PAT in the PB window. Click Test connection & the test succeeded.

Ver: PB2019R3 Build 2728
  1. Helpful 1
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.