CoSign: Collaborative Single Sign-On  

cosign-discuss at
general discussion of cosign development and deployment

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Apache 2 and Cosign

I checked my logs and I am not seeing any cert errors. I do however see input read failed errors. I sent Brett a copy of the logs. I will attach here as well.

Attachment: weblogin
Description: Binary data

On Jun 20, 2004, at 9:18 PM, Bradford R. Battey, Jr. wrote:

I had this very same issue with my recent install with Cosign 1.6.1 and
Apache 2. The CA Certs I copied over weren't able to be accessed by the
user apache is running as. Fixing that fixed the problem.

My logs showed something along the lines of:

snet_starttls: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed


On Sat, 19 Jun 2004, Brentley S.Felton wrote:

First off I would like to thank Johanna for her patience in working
with me. I have the following issue with Cosign. If I turn
CosignProtected On on any directory or file I wish to protect I face
the infamous Error 503 Service Temporarily Unavailable. My question is
- Is this a common issue with apache2 and cosign, if so is there
something that I can do to correct this? If more info is needed let me
know and I can supply.

Thanks in advance!


Copyright © 2002 - 2004 Regents of the University of Michigan :  Page last updated 15-December-2010