Issuer for SubVersion certificate not accepted by SVNSCC plug-in

( SVNSCC , Quest Toad, 1.6.x, WIN 2000/XP, x86 )

Type: Public Status:Closed Created: 31 Aug 09 08:00 Updated: 01 Oct 09 10:00

You value our support on this issue as "bad, some feedback is provided but it not help me". Click here to resubmit your opinion.

--> Aleksey Kochetkov (admin) at 01 Oct 09 10:00 writes

Unfortunately we could not repeat this error.
I passed your information in the department of development, they recheck
work with certification and correct errors if they exist.

--> christophe.galibert (user) at 29 Sep 09 09:00 writes

Hi,

No news until today, do you expect when you will have results for your test
?

--> Aleksey Kochetkov (admin) at 01 Sep 09 09:00 writes

We'll test this situation, as soon as we receive the results, immediately
write to you about them.

--> christophe.galibert (user) at 31 Aug 09 08:00 writes

When connecting to a SubVersion repository by https protocol, PushOK SVNSCC
says that the server certificate is not issued by a trusted authority.

By using SubVersion command-line client, no error, repository can be
accessed without warning message.

The certification authority which delivered the SubVersion server
certificate is a trusted certification authority, an internal trusted
authority. Root certificate is well installed on workstation. We tried to
delete the root certificate and without it, SubVersion command line raises
the same message as SVNSCC.

It seems like SVNSCC does not recognize the trusted authority.

Is there some parameter to avoid this ? We can accept the warning message
(and permanently accept certificate) but we should not have to do this.

Thanks.

Rate this ticket:

Not useful at all

Partially useful

Useful

Very useful

Ticket

Issuer for SubVersion certificate not accepted by SVNSCC plug-in