Hi All, I have been working on setting up a new cosign protected service, based on an existing and working configuration. The existing machine works flawlessly, but the new one produces the follow error messages, and errors when validating the cookie.
[Wed Aug 08 09:20:57 2012] [error] mod_cosign: connect_sn: connect [Wed Aug 08 09:20:57 2012] [error] mod_cosign: connect_sn: connect [Wed Aug 08 09:20:57 2012] [error] mod_cosign: connect_sn: connect [Wed Aug 08 09:20:57 2012] [error] mod_cosign: connect_sn: connect [Wed Aug 08 09:20:57 2012] [error] mod_cosign: connect_sn: connect [Wed Aug 08 09:20:57 2012] [error] mod_cosign: connect_sn: connect [Wed Aug 08 09:20:57 2012] [error] mod_cosign: cosign_cookie_valid: Unable to connect to any Cosign server. I'm not sure what other information would be useful. I can resolve the weblogin server from the service as apache, and the command (as apache): openssl s_client -connect weblogin.umich.edu:6663 -cert ./ssl.cosign/cosign.cert -key ./ssl.cosign/cosign.key -CApath ./ssl.ca -showcerts -state -debug -crlf -starttls smtp shows me connected without error and displays the certificate as expected and without error. I've tried google-fu to find a solution, but I haven't found any pages that have this combination of connect_sn: connect and unable to connect. Thanks in advance, Ross Smith ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Cosign-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cosign-discuss
