[an error occurred while processing the directive]

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

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

upcoming features in IIS filter?

To: Cosign Discussion <cosign-discuss@xxxxxxxxx>
Subject: upcoming features in IIS filter?
From: Phil Pishioneri <pgp@xxxxxxx>
Date: Thu, 09 Sep 2004 11:25:06 -0400
User-agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a3) Gecko/20040817

Can anyone give more details on these new parameters for a future version of the IIS ISAPI filter?

You can now specify allowUnauthenticatedAccess to <Protected/> pages.
example:
<Protected allowUnauthenticatedAccess="TRUE">/MySweetWebApp</Protected>

and

Added <RequireAuthN/> option. This was added because the IISCosign dll does not follow the Apache rules of specifying cosign authentication.

-Phil

Follow-Ups:
- Re: upcoming features in IIS filter?
  - From: Jarod Malestein

Prev by Date: RE: IIS Cosign failure mode - security hole?
Next by Date: Re: upcoming features in IIS filter?
Previous by thread: RE: IIS Cosign failure mode - security hole?
Next by thread: Re: upcoming features in IIS filter?
Index(es):
- Date
- Thread

[an error occurred while processing the directive]