On August 16, 2012 14:43 , Shawn Rahl <[email protected]> wrote:
> We are getting the 503 Service Temporarily Unavailable message after 
> authenticating with weblogin. [...]
>
> Differences between production and this config:
> - site name is mitools-dev instead of mitools
> - IPs are different
> - certs are self-signed instead of GeoTrust certs
>
> Here is what we are seeing:
>
>     In the error log (mitools-ssl-error_log), we see:
>
>         [Thu Aug 16 14:39:50 2012] [error] mod_cosign: snet_starttls:
>         error:14090086:SSL
>         routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
>

The above error suggests to me that mod_cosign is not able to verify the 
certificate that the central weblogin servers use to identify 
themselves.  Run the command

openssl s_client -connect weblogin.umich.edu:6663 -cert 
/etc/pki/tls/certs/minos.lsa.umich.edu.crt -key 
/etc/pki/tls/private/minos.lsa.umich.edu.key -CApath /etc/pki/tls/certs 
-starttls smtp -showcerts

in order to see what certificate your central weblogin servers use, and 
who signed it.  Change "weblogin.umich.edu" above to be the name of your 
organization's central weblogin servers, and change the certificate 
filename, the key filename, and the CApath (path to the directory 
containing the certificate authority root and intermediate certificates 
and hashes) as appropriate for your web server.

In the output, you should see lines similar to the following:

Server certificate
subject=/C=US/ST=Michigan/L=Ann Arbor/O=University of 
Michigan/OU=ITCS/CN=weblogin.umich.edu/[email protected]
issuer=/C=US/ST=Michigan/L=Ann Arbor/O=University of 
Michigan/OU=ITCS/CN=UM Web CA/[email protected]

In this case, the central weblogin server certificates have been signed 
by the certificate authority "UM Web CA".

Make sure you have the root certificate for this CA installed (from the 
information you included in your original message, you do have it 
installed).

ALSO make sure that you have created a hash for the certificate in the 
same directory -- from your original message, you seem to be missing 
this, and this is likely the cause of your problem; let us know if you 
need instructions on how to create / manage certificate hashes.

Finally, the central weblogin servers at most (all?) institutions won't 
accept self-signed certificates from client web servers.  Find out what 
certificate authorities your institution's central weblogin servers 
trust, and get a certificate for use with cosign that is signed by one 
of these CAs.  If you really want to, you can use a self-signed 
certificate for HTTPS, but you almost certainly will need a 
non-self-signed one for the mod_cosign CosignCrypto directive, even 
though this is a development server.  Many institutions will provide a 
no-cost option for this (your institution happens to provide two no-cost 
options: the InCommon certificate service [commercially signed and 
widely trusted], and UM Web CA [locally signed]).

I hope this helps.  If addressing these two things (creating a hash for 
the root CA certificate for the certificate used by your central 
weblogin servers, plus using a non-self-signed certificate in the 
CosignCrypto directive) do not get everything working, please let us know.

--
   Mark Montague
   [email protected]


------------------------------------------------------------------------------
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

Reply via email to