Hi,
I have an IIS7 server running a cosign protected website successfully, but now
I'm trying to add a second cosign protected website (veterans_test_separated)
to the same webserver.
The second site works fine (correct SSL cert) until I turn on cosign
protection. With cosign protected status="on",visiting
https://veterans.onsp.umich.edu/test.html brings up a weblogin screen. After
correctly providing credentials, I get "Internet Explorer cannot display the
webpage." I also get the following error in the webserver event log:
Faulting application name: w3wp.exe, version: 7.5.7600.16385, time stamp:
0x4a5bd0eb
Faulting module name: CosignModule.dll, version: 0.0.0.0, time stamp: 0x4ce43995
Exception code: 0xc0000417
Fault offset: 0x000000000001d7d4
Faulting process id: 0x8d0
Faulting application start time: 0x01cbe2618d55bff0
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: c:\windows\system32\inetsrv\CosignModule.dll
Report Id: cb2ad3e8-4e54-11e0-8f8f-00155d73e80a
I've been banging my head on this for a while and would really appreciate any
help.
--Brian
Here is my web.config file in the veterans_test directory:
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<system.web>
<sessionState mode="InProc" timeout="6000" />
<compilation debug="true">
<assemblies>
<add
assembly="System.DirectoryServices,Version=1.0.3300.0,
Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a" />
</assemblies>
</compilation>
</system.web>
<system.webServer>
<cosign>
<webloginServer name="weblogin.umich.edu"
loginUrl="https://weblogin.umich.edu/?"; port="6663"
postErrorRedirectUrl="https://weblogin.umich.edu/post_error.html"; />
<crypto certificateCommonName="veterans.onsp.umich.edu" />
<cookieDb directory="C:\inetpub\temp\Cosign Cookie DB\"
expireTime="120" />
<proxyCookies directory="C:\inetpub\temp\Cosign Proxy DB" />
<validation validReference="https?://.*umich\.edu(/.*)?"
errorRedirectUrl="https://weblogin.umich.edu/cosign/validation_error.html"; />
<cookies secure="true" httpOnly="true" />
<service name="cosign-veterans.onsp" />
<protected status="on" />
</cosign>
<handlers>
<add name="Cosign Validation" path="/cosign/valid*" verb="*"
modules="Cosign" resourceType="Unspecified" />
</handlers>
<modules>
<add name="Cosign" />
</modules>
<httpErrors>
<error statusCode="503" path="/503.html" responseMode="ExecuteURL"
/>
</httpErrors>
<defaultDocument>
<files>
<add value="index.aspx" />
</files>
</defaultDocument>
</system.webServer>
<location path="veterans_test_separated/cosign/valid">
<system.webServer>
<cosign>
<protected
status="off" />
</cosign>
</system.webServer>
</location>
</configuration>
If it would be helpful, I can provide my applicationHost.config file as well.
--Brian
------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
Cosign-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cosign-discuss
