Posted last week and still have an issue with our IIS Cosign filter. Running
2.0.3. Users are getting directed to logon page and that is successful but then
are denied access to the page. Seeing to errors in Cosign log and event log.
Wonder if someone might be able to point me in the right direction. Filter was
working at version 1.X last week. Broke when I upgraded to 2.0.3. I removed the
entire 1.X filter along with entire IISCosign directory and reg setting. Wish I
didn't do that now. I reset permission per readme. This server was a Windows
2000 IIS server that was upgraded to Windows 2003. Errrors I'm seeing that
might be clues as to the problem.
Windows application log.
Could not initialize log file C:\Program Files\IISCosign\Logs.
Cosign log.
[5-4-2008 13:21:20] OnPreprocHeaders(): Could not get cookie.
Almost makes me think a process doesn't have correct permission in the log and
cookieDB directories. There are no files in the cookieDB directory as yet. The
cosign log file appears to be collecting information. Interesting in the log
file error above. If the cosign log file is collecting events what is the can't
init log file all about.
Need to get the filter back online soon as we have some important campus
applications on this server.
Craig Farrell
Assistant Director of Information Technology
Penn State Altoona
3000 Ivyside Park
Altoona PA 16601
(814) 949-5295
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Cosign-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cosign-discuss
