Subversion in Intellij keeps asking for authentica

2020-03-01 05:53发布

问题:

I hope someone can help me solve this frustrating issue that I am having.

I am trying to checkout a project from subversion but for some reason it doesn't let me.

At first when I put the URL, it gives me options such as whether I want to authenticate via password,ssh agent or ssh key etc. I choose the authentication with password option. At this stage the login is successful as I can browse my repository.

However, when I go to checkout a project from my repository, it asks for authentication again; I input the password but it keeps asking for the password again

The following window keeps popping.

I have tried the following solution without success:

  • Cleared the authentication cache from the intellij subversion settings.
  • Uninstalled and installed intellij again
  • Found online that the following line might help if added to idea.exe.vmoptions

    -Dsvnkit.http.methods=Basic,Digest,NTLM

but this didn't work either.

Any advice?

回答1:

In IntelliJ, the problem can be solved using the following steps for the following versions.

IntelliJ 2018.1

  • Go to Settings -> Version Control -> Subversion
  • Check the option Enable interactive mode.

IntelliJ 14

  • Go to Settings -> Version Control -> Subversion
  • Uncheck the option Use command line client.


回答2:

You can go to the svn console and perform any svn command like:

svn list https://www.repo.rr.com/svn/main/team/gaurav

Then svn promt password and ask if you want to save password. If you save password, Intellij will see the password too.



回答3:

When I checkout the project, I have to set a few options such as directory location, subversion version. I checked the 1.7 version instead of the 1.8 one and it worked. So I guess it was something to do with using the wrong version of subversion. This was on windows 7, intellij 13.1.4

Hope it helps



回答4:

Just to add: I had the same problem, and it turned out that (at least on Windows), it was using the "svn" command-line client, which happened to be version 1.7 (and I think my server is on 1.8). So I solved the problem by going into settings and unticking the "Use command-line client" option. Then it worked fine, presumably using its internal svn client.