|
cosign-discuss at umich.edu
|
general discussion of cosign development and deployment
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: multiple cosign configuration and runtime issues
* johanna bromberg craig <canna@xxxxxxxxx> [041110 17:04]:
>
> >My CosignCrypto looks like this:
> >
> >CosignCrypto /var/cosign/certs/key.pem /var/cosign/certs/cert.pem
> >/var/cosign/certs/CA
> >
> >Shouldn't mod_cosign be looking for /var/cosign/certs/key.pem?
>
> yes, you are 100% correct. This is why i think it's the logout cgi. :)
>
You mean things don't work well if you're using a 1.7.0 cosign.cgi with
an older logout cgi? :o
Um, yes that seems to be the bulk of the problem <sheepish_blink>. Oh
dear oh dear oh dear.
Well with *that* out of the way things seem to be working a *lot*
better. Logouts generate no longer generate errors (and none of those
silly symlinks are needed). My cosign cookies are working on the
weblogin server itself as well as on a separate server.
Thanks for your patience!
I do notice a variable delay of a few seconds to a few minutes for
logout actually takes effect (i.e. after I logout I can still access a
cosignprotected location for as long as a couple minutes). It doesn't
seem to be related to browser caching. Is this a known issue?
Ben
|