SVN Web Client 3.1.0 hangs when configuring for HTTPS repo

[sayalik]

I am using SVN Web Client 3.1.0 deployed on Tomcat 7.0.2.
My svn repository is accessible over HTTPS and I configured the same in web.xml
When I try to access the web client, the client as well as Tomcat both hang.
Kindly let me know if I am doing some thing wrong or any other way of configuring the client.

Thanks & Regards,
Sayali Kumbhar

[Anto]

I got a similar problem. I tried to set-up Polarion SVN Web Client 3.1.0 for a HTTPS SVN repository but it hang up. When I change to HTTP everything works fine but I still want to use the more secure HTTPS. Does anyone know how to solve this problem or is a known bug? If so, is there any chance for a patch, new version, etc. ?

Best regards
Anto

[E-Penguin]

I'm also having the same problem.

Anybody know what this "ProtocolKeyFile" is supposed to be set to?

[NickEntin]

Hi,

tip from our developers:

in order to configure HTTPS ProtocolKeyFile and ProtocolPassPhrase settings should be specified (uncommented and set to real values) in web.xml, as it's described in the section "IV. Supported protocols" of readme.txt.

Best regards,
Nick

[E-Penguin]

Hi,
thanks for the reply.

The problem is that nowhere is it described exactly what this protocol key file is supposed to be. I guess it's some sort of SSL certificate, but where does that come from?

I tried using the Tomcat SSL keyfile I set up to allow Tomcat to use SSL, but that didn't work.

Thanks,
Daniel

[harrisonford861]

I think, its better to have SSL certificate when you setup something online !

[abeha]

When I try to access the web client, the client as well as Tomcat both hang.
Kindly let me know if I am doing some thing wrong or any other way of configuring the client.

[E-Penguin]

I eventually worked out how to extract the required keyfile, from the Tomcat java keystore used to host the server:
https://security.stackexchange.com/ques ... l-keystore

[Anguo]

For me, it is a problem caused by my self-signed certificate of apache server. SVNkit(java svn connector) must verify the svn server's cert before setup connection. There's a key points, your self-signed cert's server name must match the host name.
The subversion use mod_dav as a http(s) service engine.
When you use Polarion SVN Web Client connect to the repo, the eclipse plugin will do a handshake with server because of your ssl configuration.
If you use a self-signed certificate for your server, the client do not trust it automatically.
You can config your tomcat account's subversion auth parameters to fix this problem, like this

Code: Select all

X@tomcat7~:sudo vi ~/.subversion/servers 


find section [global], add following 2 lines

Code: Select all

[global]
ssl-authority-files = /etc/ssl/certs/server.crt(use your certs here);...
ssl-trust-default-ca = yes


Alternatively, maybe you can't switch to user tomcat7, you also can set up the subversion server to be trusted globally for every user.

Code: Select all

X@defaultuser~:sudo vi ~/etc/subversion/servers 


the configuration is same as previous.

This works for me. Good luck, guys

Anguo

[kimmysawi]

I'm also having the same problem.

Anybody know what this "ProtocolKeyFile" is supposed to be set to?

Same, i am facing the same problem, resolve it as soon as possible