On Mon, Jun 30, 2008 5:59 PM, Sacha Michel Mallais 
<[EMAIL PROTECTED]> wrote:
> The next problem is that its complaining that it can't connect to any 
> server:
> snet_starttls: error:14090086:lib(20):func(144):reason(134)
> snet_starttls: error:14090086:lib(20):func(144):reason(134)
> snet_starttls: error:14090086:lib(20):func(144):reason(134)
> snet_starttls: error:14090086:lib(20):func(144):reason(134)
> Unable to connect to any Cosign server.
>
> I found this message talking about problems with certs: 
> http://weblogin.org/cosign-discuss/msg00222.html.  I'm using a 
> self-signed cert, is that bad?  Do I need to have my cert signed by 
> someone at the cosign server?

The certificate must be signed by a CA that is trusted by the central 
cosign weblogin servers that you are using.  It is possible to configure 
an organization's weblogin servers to accept self-signed certificates, 
but doing so offers few advantages and is not a standard configuration.

Contact the people who run your organization's weblogin servers to find 
out which CAs your weblogin servers trust.   [ I'll reply to you 
off-list with information about the University of Michigan weblogin 
servers. ]

                Mark Montague
                ITCS Web/Database Production Team
                The University of Michigan
                [EMAIL PROTECTED]



-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Cosign-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cosign-discuss

Reply via email to