Bitbucket clone to Sourcetree, repeatedly asking for password - bitbucket

I am completely new to Bitbucket and Sourcetree. I have received a repository from my college, when I log into Bitbucket I find it there with all necessary files. I would like to clone it, so i can work with it on my laptop, so I drag it from the website to the Sourcetree window and get requested Source URL, Destination path and Name. Here the problems start, I get repeatedly asked for password, but the password is correct. Do someone have any suggestions? I am running OS X El Capitan Version 10.11.6
Thank you!

I came across the same issue on SourceTree 2.7.3 under OS-X 10.13.6. I was given access to a repository over https and had to clone it. Since even the cloning failed through SourceTree due to "password keep asking issues", I cloned it through Terminal which worked fine. Post that, I could open the locally cloned bitbucket repo through SourceTree, but any git remote operations continue to fail over "password keep asking issues".
I came across several possible workarounds through several posts like
https://community.atlassian.com/t5/Sourcetree-questions/Sourcetree-keeps-asking-for-bitbucket-password-on-windows/qaq-p/241278
https://community.atlassian.com/t5/Sourcetree-questions/Sourcetree-keeps-asking-for-login-and-password/qaq-p/146765
https://community.atlassian.com/t5/Sourcetree-questions/SourceTree-2-7-constantly-asks-for-credentials/qaq-p/711139
https://community.atlassian.com/t5/Bitbucket-questions/Bitbucket-clone-to-Sourcetree-repeatedly-asking-for-password/qaq-p/704242#U919139
Suggested workarounds were
Using latest out of embedded or system git versions and reopened SourceTree
Upgraded SourceTree from 2.7.3 to 2.7.6
Clearing bitbucket entries from keychain and reopened SourceTree
Clearing bitbucket sourceTree cached passed file from ~/Library/Application Support/SourceTree/ and reopened SourceTree
Did not try to downgrade from 2.7.3 to 2.6.3 as suggested by one post wondering what worse might wait for me with an older version :-)
Even restarted the machine without any luck.
At this point, I noticed that my Mac's Gmail synching went offline after sometime due to login issues. Then I recalled that my Atlassian account address is the Gmail-id I used for OAuth integration with BitBucket User. And, sign-in to bitbucket was successful too through SourceTree's Accounts option. It is the subsequent git remote operations through SourceTree UI was suffering and now os-x Gmail synching too.
Then, I kept the password of Atlassian's user id(which is my Gmail id) to same as that of Gmail id. And, restarted the machine. Voila.. it all started working fine including Gmail synching and SourceTree.
Wondering if the password chosen for Atlassian account, which is the same as the Email-id used for its OAuth integration, did corrupt SourceTree's key-chain entries for HTTPS access. That sounds ridiculous and a critical bug. sigh!!!

Related

Jenkins "Invalid Username and Password" PAM Authentication

I am running Jenkins 2.164 in RHEL with Centrify as AD connector. I have configured Jenkins security to use PAM. The PAM security configuration test is Success and Matrix Security is also able to validate users and group via PAM. When restarting Jenkins and login, it doesn't seem to be able to authenticate via PAM and keeps getting "invalid username or password error". I am using Pam-Auth plugin version 1.5. The weird part is when I am using an older version of Jenkins 2.89, it works. Also, the new Jenkins has changed the login form to a SimpleLogin and I suspect that causes incompatibility with my Centrify.
I have checked the /var/log/messages file and I keep receiving the following error. This has never happened before in the older version. I am not sure why the older version of Jenkins works but not the current version I'm using.
I've tried to swap to an older version of libpam4j-1.8 before pam_setcred was being introduced in 1.11 version, but still fail.
Any help would be greatly appreciated.
Apr 24 23:45:26 adclient[35963]: INFO AUDIT_TRAIL|Centrify Suite|PAM|1.0|201|PAM set credentials
denied|5|user=test(type:ad,test#testdomain.com) pid=180 utc=1556163926715 centrifyEventID=24201 status=DENIED service=sshd tty=(none) client=(none) reason=Failed to set user credentials

Stop GitKraken asking for login credentials

GitKraken has successfully cloned a repository hosted on Team Foundation Server, but on subsequent fetch and push it asks for login information. Even when provided it will ask again, offering no error or explanation. "Remember me" is checked.
Everything works perfectly fine using the cmd.
Note that the issue occurs on a virtual machine. I have tested interacting with the repository on my physical machine using GitKraken - no problem there. However, I have previously experienced the same type of problem with other projects on my physical machine. Seems GitKraken sometimes has problems with TFS, but not sure.
I have tried reinstalling GitKraken, but it didn't resolve the issue. Any ideas on how to fix this?
Edit 2018-01-24 as per #Cece Dongs comment
I am using GitKraken 3.3.3 - recently upgraded, but issue still occurs.
TFS is version 15.117.26714.0 and using the web portal does not give me problems. I login once like normally.
When cloning a GitHub repo everything is working properly. However, when attempting to clone a TFS repo from Visual Studio I get an unauthorized error. (TF30063). I assume it could be related to the Active Directory settings not set up properly because of the Hyper-V setup I am using. Will investigate further and provide more details here.
After using \domain\username instead of just username as login credentials to TFS everything is working.
Using only the username will work on my physical machine as that machine is recognized on the domain, but as the virtual machine is not, the domain is required.

No supported authentication methods available (server sent: publickey)

I have created ssh key using the command ssh keygen and I have added the public key to my bitbucket account and then I have added the key to the ssh agent also, But when I tried to clone repo from bitbucket using sourceTree, I am getting the below Error.
Error: FATAL ERROR: Disconnected: No supported authentication methods available (server sent: publickey)
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
and I know this is repeated question but those solution didn't worked for me, So please help.
Well, It was my mistake actually,
SSH Client type was set to PuTTY/Plink in my SourceTree Settings, So I changed it to openSSH and now that issue is no more.
Sorry & Thanks.
I am using SourceTree to access an enterprise GitHub server, and had the same issue all of a sudden start occurring to me even though it has been working fine for over a year and nothing had changed. Apparently, somehow my SSH Client Type was swapped to PuTTY/Plink. Switching it to openSSH again fixed the issue for me by going to Tools -> Options -> General -> then selecting OpenSSH as the SSH Client under the SSH Client Configuration section.
Changing the SSH Client type to openSSH in Source Tree - tools -> Options -> General solved this error for me.
(I posted the following to atlassian.com bug report)
We had the same issue. We noticed that the Pageant (in the icon tray) would not start.
For us it appears that our antivirus was blocking it somehow. Thus we do the following:
disabled the antivirus
uninstall SourceTree (SourcetreeEnterpriseSetup_3.4.6.msi)
installed SourceTree (SourceTreeSetup-3.4.6.exe)
reconfigured SourceTree
We noticed that Pageant was now running and ssh calls worked.
Reenabled the antivirus.
So far so good.
In my case, I was getting same error but the "pageant" program installed was very very old, but worked after updating it (via the putty installer). Credit to https://superuser.com/users/106302/fabian # https://superuser.com/a/404286/658383

Version 7.1 (7B91b) and TFS Authentication [duplicate]

We are working on Xcode Project connected to our local TFS 2013 (Update 3) Server via TFS Provided Git Repository.
When we use older version of Xcode, we are successfully able to check-in the files and perform all other Git operations. We are also able to perform all Git Operations via command line Git.
The trouble is when we use latest version of Xcode - Version 7.1 (7B91b).
On entering valid credentials, we are getting error saying
Authentication failed because the user name or password was incorrect.
The same credentials / configuration work on older version of Xcode and Git Command Line Options.
To add more to the surprises, we are able to connect to github.com successfully.
We are able to reproduce issue on other systems too. Please provide us the best way to resolve this error.
For us it turned out to be because Xcode 7 does not support Windows Authentication. The solution described here solved it for us:
"This happens because XCode 7 doesn't support Windows Authentication.
I don't know why. It seems to be a common problem amongst users
because there are many posts about it in google.
To make it all work you should enable Basic Authentication in your IIS
TFS website on "tfs" virtual folder.
Be careful though because basic authentication sends your credentials
over network as plain text. You definitely must use SSL in this case."
(source)

Xcode 7 Git can’t find remote repositories

I could push & pull this repository without any problems on Xcode 6.X, but it doesn’t work on Xcode 7.
The setting is the same as Xcode 6.X. I tried to enter Username and Passphrase just for confirmation, but seems like no meaning. I used the right SSH Keys as Authentication, but the preferences say “The remote repository could not be found.”
Checking out a new repository, that have been never used on Xcode 6.X ,also had the same issue on Xcode 7.0 and higher.
I’d like to know if anyone has any solutions for this problem.
"could not be found" is also the error message you see when you access a repo you don't own (instead of a "permission denied")
For security reason, one does not confirm or deny the existence of a repo, one simply state "it cannot find it".
So make sure the repo exists, that your are the owner and that your public key is registered to your account.
Since that issue seems limited to XCode7, it was reported before, and could be linked to a cipher issue (XCode7 refusing to establish a connection with an sshd working with a cipher too weak)
I have an easy solution if your remote is set and suddenly when you can't pull because of "no remote repository found" message. Go to terminal. Open your project folder. do
git pull origin v6.2
If you have commits that were not made, you might have to:
git reset --hard
git commit -m "Commit Message"
After you pull it one, you will be able to pull more with no problem from Xcode.

Resources