This is a Cosign question, but rather narrowly focused on the U of Michigan environment. Apologies is this is clutter or inappropriate use of the list.
Lately I've been having users on UMHS networks (141.214.) have trouble authenticating to Cosigned services at the College of Engineering, and elsewhere, including wolverineaccess.umich.edu. I can see log entries for /cosign/valid? requests piling up as they get redirected back to weblogin.umich.edu repeatedly. Eventually their own browser will detect a redirection loop and stop the madness. They are always 'coming from' the same IP address at UMHS when this occurs. Is there some known issue with UMHS networks or configurations that would explain this? Is there a recommended setting for CosignCheckIP that I should be using? This seems like a newish issue - never had any reports of it before, but now several in the last few weeks. Thanks for any advice, -t ____________________________________________ Thomas Knox College of Engineering, University of Michigan ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Cosign-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cosign-discuss
