This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Sometimes happens that certificate accept dialog is endlessly shown. Steps: 1. Invoke "Check out" wizard with empty user dir. 2. Enter some "Repository URL" with "https://" Accept dialog is shown over and over again.
Created attachment 30786 [details] svn.ssl.server
*** Issue 79966 has been marked as a duplicate of this issue. ***
Increasing priority to P2.
Probably fixed. There was no validity check on the certificates send from the server, so it could happen that the svn module was all the time trying to use an expired one. Checking in SvnClientExceptionHandler.java; /cvs/subversion/main/src/org/netbeans/modules/subversion/client/SvnClientExceptionHandler.java,v <-- SvnClientExceptionHandler.java new revision: 1.20; previous revision: 1.19 done merged into 5.5 and 5.5 beta2
I just downloaded the subversion module 1.1 for windows netbeans 5.5 beta2. I would love to try it but it won't allow me to download my sources. Every time I try to connect to my https server, it provides me with a window "Server certificate verification failed" that provides the following info: - The certificate is not issued by a trusted authority. Use the fingerprint to validate the certificate manually! - The certificate has expired. Certificate information: - Hostname: svn.mydomain.com - Valid: from 7/25/06 3:50 PM until 8/24/06 3:50 PM When I try to accept permanently or temporarily it redisplays the "Server certificate verification failed" window again. This continues as long as you want to click on accept perm/accept temp. The funny thing is why does it say "The certificate has expired" when I just created the certificate? I ran at Tue Jul 25 16:25:59 PDT 2006. BTW, this does correctly work with the svn command line client and the TortiseSVN client.
could you please run netbeans with the switch -J-DsvnLog=PATH_TO_A_FILE and attach this file and also attach the messages.log generated by netbeans? are your sources on some public server so i could try it out by my self?
"nothinbutnet" please, provide required details. We can't reproduce it.
nothinbutnet: do you stil have the problem?
fixed in trunk Checking in SvnClientExceptionHandler.java; /cvs/subversion/main/src/org/netbeans/modules/subversion/client/SvnClientExceptionHandler.java,v <-- SvnClientExceptionHandler.java new revision: 1.23; previous revision: 1.22 done Checking in Bundle.properties; /cvs/subversion/main/src/org/netbeans/modules/subversion/client/Bundle.properties,v <-- Bundle.properties new revision: 1.9; previous revision: 1.8 done and 5.5 Checking in SvnClientExceptionHandler.java; /cvs/subversion/main/src/org/netbeans/modules/subversion/client/SvnClientExceptionHandler.java,v <-- SvnClientExceptionHandler.java new revision: 1.11.4.11; previous revision: 1.11.4.10 done Checking in Bundle.properties; /cvs/subversion/main/src/org/netbeans/modules/subversion/client/Bundle.properties,v <-- Bundle.properties new revision: 1.4.2.7; previous revision: 1.4.2.6 done
Verified.
*** Issue 84473 has been marked as a duplicate of this issue. ***
*** Issue 86798 has been marked as a duplicate of this issue. ***
Sorry for not getting back with you. I upgraded my svn to 1.4.0 then I just tried the svn module Version 1.1.20.42.1.1 and I had the same problem I had before. I read your comments and knew there had was something different between our systems. The one obvious thing that was probabally different between our systems was that I was using an expired certificate. Thinking this was the case I generated some new certifiates (both server and ca) and the problem went away. So to reproduce this issue try using an expired server and ca sertificate.
thanks for the hint, but i'm missing your point. In the post from Jul 26 you wrote that your cerificate wasn't expired and now that it was. the fact is, that we could reproduce the issue with different scenarious (also with an expired certificate) and the fix seemed to work. feel free to reopen if you are still _able_ to reproduce it.
I did see the problem again, however I now have a workaround. I won't reopen this issue but if users continute so see this problem again ask them to upgrade their client and ca certificates. perhaps you could place a statement like "always use vaild certificates if you expericed authenticaion problems usin svn with netbeans." At least future users with this problem can search for this issue to resolve their problem. I do appreciate all the great work everyone has done whith svn integration in netbeans. Thank you.
ok, so in your case it seems to be just a expired certificate problem, am I right?
Currently my problem was fixed by upgrading my certificates so I would say that all other problems have been fixed. TortiseSVN and the commmand line still allow me to access the repository with an expired certificate though. Perhaps another bug should be created and leave this one closed since the expired certificate dialog still says you can temporarily accept the expired certificate but cannot.
Verified in NetBeans IDE Dev (Build 200610261800)