The mode is set on the Application Pool.  This article might help:
http://learn.iis.net/page.aspx/243/aspnet-integration-with-iis-7/

Bill


On Mon, May 17, 2010 at 12:05 PM, Cary, Kim <[email protected]> wrote:
> Scott, I'm woefully ignorant as an IIS admin, as is my windows admin 
> (exchange is the first thing they've set up on iis7). How can we tell which 
> mode we are in? KC
>
> On May 17, 2010, at 6:30 AM, Scott M. Holodak wrote:
>
>> I'm not sure if this is the problem you're seeing or not, but handlers
>> and modules need to be configured differently in IIS 6 and 7.  The
>> following style of configuration works on IIS 5/6 and 7+ (in Classic or
>> Integrated Pipeline mode).
>>
>> <configuration>
>>    <system.web>
>>        <!-- IIS 5/6 & IIS 7+ Classic Pipeline configuration -->
>>        <httpHandlers>
>>            <add verb="*" path="MyHandler.asx" type="Example.MyHandler,
>> Example" validate="false" />
>>        </httpHandlers>
>>        <httpModules>
>>            <add name="MyModule" type="Example.MyModule, Example" />
>>        </httpModules>
>>    </system.web>
>>    <system.webServer>
>>        <!-- IIS 7+ Integrated Pipeline configuration -->
>>        <validation validateIntegratedModeConfiguration="false"/>
>>        <handlers>
>>            <remove name="MyHandler" />
>>            <add name="MyHandler" verb="*" path="MyHandler.asx"
>> preCondition="integratedMode" type="Example.MyHandler, Example"/>
>>        </handlers>
>>        <modules>
>>            <remove name="MyModule"/>
>>            <add name="MyModule" type="Example.MyModule, Example" />
>>        </modules>
>>    </system.webServer>
>> </configuration>
>>
>>> -----Original Message-----
>>> From: Francisco Estanqueiro [mailto:[email protected]]
>>> Sent: Saturday, May 15, 2010 7:39 AM
>>> To: [email protected]
>>> Subject: RE: coa/auth not redirecting Re: [cas-user] CAS ClearPass
>>> Outlook .NETCASClient integration on IIS 7
>>>
>>> According to the author of CasOwa in IIS 7 you have to setup this
>>> handlers:
>>>
>>>>>>>> Requirements
>>>>>>>> * CAS Server with ClearPass extension configured to accepted
>>>>>>>> ProxyTickets from CasOwa.
>>>>>>>>
>>>>>>>> Installation
>>>>>>>> Deploy CasOwa in its Virtual Directory on the same IIS server
>>> that is
>>>>>>>> running.  This is to ensure that the authentication cookies set
>>> by
>>>>>>>> CasOwa will be visible to OWA.  Managed Pipeline Mode for this
>>> Virtual
>>>>>>>> Directory should be set to Integrated.
>>>>>>>>
>>>>>>>> Http HandlerMappings
>>>>>>>> CasOwa requires two HandlerMapping configurations, one for
>>>>>>>> CasOwaAuthHandler and one for the DotNetCasProxyCallback.
>>>>>>>>
>>>>>>>>       CasOwaAuthHandler Mapping
>>>>>>>>       Request path: auth
>>>>>>>>       Type: CasOwa.CasOwaAuthHandler
>>>>>>>>       Name: CasOwaAuthHandler
>>>>>>>>
>>>>>>>>       DotNetCasProxyCallback Mapping
>>>>>>>>       Request path: proxyCallback
>>>>>>>>       Type: CasOwa.CasOwaAuthHandler
>>>>>>>>       Name: DotNetCasProxyCallback
>>>>>>>>
>>>>>>>> Http Modules
>>>>>>>> CasOwa requires one Http Module configuration for the
>>> DotNetCasClient.
>>>>>>>>
>>>>>>>>       DotNetCasClient Module
>>>>>>>>       Name: DotNetCasClient
>>>>>>>>       Type: DotNetCasClient.CasAlternateAuthModule
>>>>>>>>       [checked] Invoke only for requests to ASP.NET
>> applications
>>> or
>>>>>>>> managed handlers
>>>
>>> I think this instructions are for IIS7 since this handlers/mappings in
>>> IIS6 are configured automatically by pointing the .net dll.
>>>
>>> Francisco
>>> ________________________________________
>>> De: Cary, Kim [[email protected]]
>>> Enviado: sexta-feira, 14 de Maio de 2010 23:35
>>> Para: [email protected]
>>> Assunto: Re: coa/auth not redirecting Re: [cas-user] CAS ClearPass
>>> Outlook .NETCASClient integration on IIS 7
>>>
>>> Thanks, Vishal. We're working from that guide.
>>>
>>> Unfortunately, steps 4-6 are completely different on IIS 7. If we can
>>> get some help figuring them out, we'll add the IIS7 steps to the docs.
>>>
>>> In fact, it looks, from our scratching around that steps 4-6 in that
>>> guide happen automatically in IIS7. The virtual path 'auth' is mapped
>>> to a casowa function and that is mapped to the isapi_net.dll (going
>>> from memory).
>>>
>>> What we can't figure out is why
>>>
>>> /coa
>>> /coa/auth
>>>
>>> are giving us 404 when
>>>
>>> /coa/license.txt
>>>
>>> gives us the page!
>>>
>>> On May 14, 2010, at 3:21 PM, Ganjoo, Vishal wrote:
>>>
>>>> Use this wiki page for initial configuration
>>>> <http://www.ja-
>>> sig.org/wiki/pages/viewpage.action?pageId=29133913>http://www.ja-
>>> sig.org/wiki/pages/viewpage.action?pageId=29133913
>>>>
>>>> - Vishal
>>>
>>>
>>> --
>>> You are currently subscribed to [email protected] as:
>>> [email protected]
>>> To unsubscribe, change settings or access archives, see http://www.ja-
>>> sig.org/wiki/display/JSG/cas-user
>>> --
>>> You are currently subscribed to [email protected] as:
>>> [email protected]
>>> To unsubscribe, change settings or access archives, see http://www.ja-
>>> sig.org/wiki/display/JSG/cas-user
>>
>>
>> --
>> You are currently subscribed to [email protected] as: 
>> [email protected]
>> To unsubscribe, change settings or access archives, see 
>> http://www.ja-sig.org/wiki/display/JSG/cas-user
>>
>
>
> --
> You are currently subscribed to [email protected] as: [email protected]
> To unsubscribe, change settings or access archives, see 
> http://www.ja-sig.org/wiki/display/JSG/cas-user
>
>

-- 
You are currently subscribed to [email protected] as: 
[email protected]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/cas-user

Reply via email to