CoSign: Collaborative Single Sign-On  
AnnouncementsDiscussion
 

cosign-discuss at umich.edu
general discussion of cosign development and deployment
 

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

Another quick question and possible bug report



Title: Another quick question and possible bug report

Hi Kevin,

How are things? I have just one quick question for you if you are able and willing. J

In your last email you detailed that you have CoSign running on 3 linux boxes. How have configured these? More specifically I am really asking if each of these boxes run the CGI and cosignd/monster or have you separated them out? Also how have you configured CoSign web servers to talk to these machine? via DNS round-robin or something else?

Also, I think I have found a bug in the CoSign package. If the client isn’t in the /usr/local/etc/cosign.conf mod_cosign gets a return of 1 from cosign_cookie_valid (ie cv = 1) which cause it to fall through to the set_cookie label, which causes an infinite loop (it set the cookie and attempt to access the CGI, and then goes back to the web resource and does it all again J ).


Thanks for you help Kevin.


------------

Brett Lomas

Integration Architect

Information Technology Systems and Services

The University of Auckland

New Zealand

Phone:          +64 9 373 599 extn 86499

Mobile:         +64 21 757 096


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