JEC Jira edge connector Git (gitlab) integration with gitoption to use token instead of ssh

[Antoine _Klee Group_]

Hi, seems from this doc that we can run scripts stored on a git repo (gitlab for example), the doc describes how to use an ssh / rsa key to authenticate as the user but not how to use https (and therefore a token for authentification). How to do that?

Best.

[Oleksii Melnyk _MOY Apps_]

Hi @Antoine _Klee Group_ 

You can find related info here -> Configure Jira Edge Connector

Set the JEC_CONF_GIT_URL, JEC_CONF_GIT_FILEPATH, JEC_CONF_GIT_PRIVATE_KEY_FILEPATH, and JEC_CONF_GIT_PASSPHRASE variables. If you are using a public repository, you should use an https format of a git URL and you don’t need to set a private key and passphrase. You can optionally set JEC_API_KEY; if this property is set in the environment, its value is used as apiKey or else apiKey from the configuration file is used.

JEC_CONF_GIT_URL

HTTPS or SSH url of the git repository

JEC_CONF_GIT_URL=git@bitbucket.com:username/test-private-conf-cem.git or JEC_CONF_GIT_URL=https://bitbucket.org/username/test-conf-cem.git

Best regards,
Oleksii

[Antoine _Klee Group_]

Hi Oleskii, infact I mean connecting to the git repo but not through ssh as it is described in this doc.

I'm basically looking for a JEC_CONF_GIT_APIKEY or JEC_CONF_GIT_TOKEN variable but something like that does not appear in the doc.

[Oleksii Melnyk _MOY Apps_]

Got it,

you're after HTTPS token auth (like a PAT) for private GitLab repos in Jira Edge Connector.

Official docs don't support it. HTTPS is public-only, private needs SSH keys. But you can create a ticket for Atlassian support.