6

Git 1.7.9.1 on Arch Linux:

git svn init -s https://app.svn.beanstalk.com/repo
Initialized empty Git repository in /path/to/repo/.git/
Authentication realm: <https://app.svn.beanstalk.com/repo:443> SVN    
Password for 'localuser':
Authentication realm: <https://app.svn.beanstalk.com/repo:443> SVN
Username: remoteuser
Password for 'remoteuser':
Authentication realm: <https://app.svn.beanstalk.com/repo:443> SVN
Username:

No matter how many times I enter my details, it never accepts them. I have logged in successfully with the same credentials in a web browser. I have also tried this without the -s, and with the --no-minimize-url flags. What's going on?

Improve this question
5
  • Do you know if it's Basic, Digest, NTLM, or Negotiate authnetication?
    – penguin359
    Mar 2, 2012 at 22:50
  • Pretty sure it's Basic.
    – Hugh Guiney
    Mar 3, 2012 at 3:29
  • Did you try svn directly? Did you try accessing the server directly per http? This probably isn't related to git or even svn.
    – JonnyJD
    Dec 25, 2012 at 16:21
  • I have the same scenario using git-svn on windows in the mingw32 shell with Git 1.8.5.5. On my Windows x64 machine I am running TortoiseSVN 1.7.5 with SVN 1.7.3 and I can connect with SVN-cached credentials through both Tortoise and SVN command line yet when I attempt to clone the same SVN url with git-svn I get the behavior described above.
    – David Alpert
    Feb 14, 2014 at 22:46
  • Apparently this problem went away for me after I entered my domain credentials (username, then password) 3 or 4 times in a row. Now my git-svn is working against the local svn repos just fine.
    – David Alpert
    Feb 15, 2014 at 18:25

3 Answers 3

Reset to default
3

@DavidAlpert's advice was correct. I fixed this by simply entering my domain credentials (username, then password) 3 or 4 times in a row.

I don't know why, but it worked for me! I repeated this as an answer here since it is easy to miss in the comments.

Improve this answer
0

I've found that it's a bug in the latest version 1.9.0, in the previous one 1.8.5.2 I can successfully authenticate.

Improve this answer
0

I faced a similar issue while using beanstalk. And the issues was really simple-

  • It asks for login user account i.e. [email protected]

  • Then password - Your account password

Then its asks for 'UserName' which is beanstalk username and different from your login email id. So enter your username when it asks for

  • Then it asks for password which is same as your account password.

Do not missed the difference between those 'user account' and 'username' things and get locked.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .