Camille B?gnis wrote: >>* https works fine (if you have a ``real'' server certificate). > > Oh well, I guess this is my problem, because I never get the > identification dialog box, just an error mesage stating URL is not > webdav (I can connect to it otherwise). What is a "real" certificate? > > You can get an idea of ours by trying to connect to: > https://svn.neodoc.biz/neodoc/ >
Yes, this is almost certainly a server certificate problem. A ``real'' certificate is a certificate signed by an authority known to Sun (VeriSign, Thawte, etc). A workaround exists but is not convenient for ordinary users: you need to ``install'' NeoDoc's self-signed certificate in the Java runtime. Unix example (the certificate here is /tmp/pixware.pem): --- /# cd $JAVA_HOME/jre/lib/security /opt/java/jre/lib/security# ls cacerts cacerts /opt/java/jre/lib/security# /opt/java/bin/keytool -import \ -alias pixware -file /tmp/pixware.pem -keystore cacerts \ -storepass changeit /opt/java/jre/lib/security# /opt/java/bin/keytool -list \ -keystore cacerts -storepass changeit --- Note: "changeit" is the real default password (as chosen by Sun) of the keystore of a Java runtime. --- PS: I'll add: "make it easy for the user to manage server certificates" to our user wish list, as it seems than nobody is using real server certificates!
