PAW - GIT Repository Connection issue

[ardi]

Hello,

We are trying to use the new PAW feature to add TM1 objects to GIT Repository, and for some reason, we cannot make it work.

We have generated the SSH Public Key / Private Key, and also saved the SSH Key to GitHub, but when we enter the Repo URL / SSH Keys in PAW, we receive an error:

TM1 Git failed to connect to remote. Reason: Failed to authenticate SSH session: Callback returned error.

Not sure if anyone else has experienced this error

Thank you

[ascheevel]

Public or enterprise Github? I ran into similar errors trying to connect on-prem PAW to an enterprise Github repo and so far haven't got it working. I suspected that the connection was being blocked/rejected by enterprise github admins but haven't confirmed that. You are using the SSH url and not the http url?

[ardi]

Public or enterprise Github? I ran into similar errors trying to connect on-prem PAW to an enterprise Github repo and so far haven't got it working. I suspected that the connection was being blocked/rejected by enterprise github admins but haven't confirmed that. You are using the SSH url and not the http url?

I am connecting to a Private Enterprise GitHub also, and my PAW is on-prem (2.0.86), so I think I am on the same situation. I am also using the SSH URL ( git@....)

Thank you for sharing

[WilliamSmith]

+1 tried to get this working today, but no avail, will keep plugging away at it and report back any success

[ZLD]

What SSH algorithm did you use to generate SSH key? If it was Ed25519, you may want to try RSA (ssh-keygen -t rsa -b 4096 -C "your_email@example.com"). Older TM1 does not support Ed25519 to authenticate to git repository.

[ascheevel]

Tried both, I get the RSA with SHA-1 no longer supported by github error.

[ZLD]

Can you try "ssh-keygen -t rsa -b 4096 -C "your_email@example.com'" to generate the RSA 4096? It is supported by GitHub https://docs.github.com/en/authenticati ... -ssh-agent.

[ascheevel]

Yep, that's what I tried using the same github documentation you linked. I can see when I add the key in Github that's it's labeled as a SHA256 key, but same error when trying to connect from TM1.

Thanks for suggestion, hopefully it works for anyone else stumbling onto this. For me, I've all but given up on IBM's flavor of GIT integration for TM1 and am designing my own github based source control and deployment pipeline.

[wcoffen]

Try $ ssh-keygen -t ecdsa -C "youremail@address"

I had an issue with a different algorithm for PA Cloud and IBM suggested "ecdsa" and it worked.

[ascheevel]

Well....that worked. Thanks @wcoffen!