We are running the IIS7 Cosign Module on Server 2008R2 SP1.
We are located at Penn State which is implementing Cosign in their
WebAccess Single Sign-on solution.
We are using Cosign to protect our helpdesk system, powered by Numara
Footprints.
I'm not sure what started it, but as described in
How often was the app pool shutting down causing the 503 error? On our
Footprints server this happens any time Webaccess is in a degraded state.
Basically, if the cosign module can't communicate quickly with Webaccess,
then it shuts down. I'd call that a bug because in my mind the module
should
