[JIRA] (JENKINS-62132) JGit won't authenticate to 2FA enabled Bitbucket, CLI git does

4 views
Skip to first unread message

mark.earl.waite@gmail.com (JIRA)

unread,
Apr 30, 2020, 5:31:02 PM4/30/20
to jenkinsc...@googlegroups.com
Mark Waite created an issue
 
Jenkins / Bug JENKINS-62132
JGit won't authenticate to 2FA enabled Bitbucket, CLI git does
Issue Type: Bug Bug
Assignee: Mark Waite
Components: git-client-plugin
Created: 2020-04-30 21:30
Environment: Jenkins 2.222.3, git plugin 4.2.2, git client plugin 3.2.1 and pre-release versions from the master branch of the git plugin and git client plugin
Priority: Major Major
Reporter: Mark Waite

I upgraded my Bitbucket account to use two factor authentication. As part of that upgrade, I needed to switch from using my actual Bitbucket password in the https credentials that clone repositories to use an app password instead.

The change from using my actual Bitbucket password to app password (personal access token in GitHub parlance) was easy for the jobs that use command line git. I changed the credential value from actual password to app password and the job continued to clone and run successfully.

Jobs that use JGit and JGit-apache were previously working correctly with the actual Bitbucket password. With the change from actual Bitbucket password to an app password, they are no longer able to clone from Bitbucket.

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo

mark.earl.waite@gmail.com (JIRA)

unread,
Apr 30, 2020, 5:34:02 PM4/30/20
to jenkinsc...@googlegroups.com
Mark Waite updated an issue
Change By: Mark Waite
I upgraded my Bitbucket account to use two factor authentication.  As part of that upgrade, I needed to switch from using my actual Bitbucket password in the https credentials that clone repositories to use an app password instead.

The change from using my actual Bitbucket password to app password (personal access token in GitHub parlance) was easy for the jobs that use command line git.  I changed the credential value from actual password to app password and the job continued to clone and run successfully.

Jobs that use JGit and JGit-apache were previously working correctly with the actual Bitbucket password.  With the change from actual Bitbucket password to an app password, they are no longer able to clone from Bitbucket.

Alternatives to avoid the issue include:
* Use CLI git instead of JGit
* Use ssh protocol ( {{g...@bitbucket.org:markewaite/bin.git}} ) instead of https protocol ( {{https://marke...@bitbucket.org/markewaite/bin.git}} )

mark.earl.waite@gmail.com (JIRA)

unread,
Apr 30, 2020, 5:34:03 PM4/30/20
to jenkinsc...@googlegroups.com
Mark Waite assigned an issue to Unassigned
Change By: Mark Waite
Assignee: Mark Waite
Reply all
Reply to author
Forward
0 new messages