5) Whats the managed pipeline mode and How do I set it to Integrated?

Managed Pipeline mode is a new unified request processing pipeline
that is exposed to both native and managed components in IIS7.  Is is
not available on IIS6.
http://learn.iis.net/page.aspx/244/how-to-take-advantage-of-the-iis7-integrated-pipeline/


This means I cant use casowa with windows server 2003? (since there's no IIS7 for ws2003)

Francisco

William G. Thompson, Jr. wrote:
On Mon, Mar 29, 2010 at 10:32 PM, Francisco Estanqueiro
<[email protected]> wrote:
Hi,

Hi, Francisco.  I'll respond inline below...


I'm trying to figure out a way to casify Outlook Web Access and I found out
about this CasOwa.

I read this thread (the few information there is about casowa),
http://www.mail-archive.com/[email protected]/msg03914.html, but
since I'm really a noob in the IIS bussiness so I have some questions.

Here's what I've done:
_________________________________________________________________
clearPass installed in my CAS server (3.4.1) with this Maven's dependency:

<artifactId>clearpass-webapp</artifactId>
 <version>1.0.1.GA</version>

in the URL: https://winserver.xtanki.local:8443/cas/clearPass
_________________________________________________________________

I have Windows Server 2003 with Exchange 2007, the Outlook Web Access is
running:

OWA: https://winserver.xtanki.local/owa

_________________________________________________________________

I've downloaded the casowa zip file, changed the web.config beans:
 <appSettings> and <casClientConfig>.

<appSettings>
  <add key="CasOwa.ClearPassUrl"
value="https://winserver.xtanki.local:8443/cas/clearPass"/>
  <add key="CasOwa.OwaUrl" value="https://winserver.xtanki.local/owa"/>
  <add key="CasOwa.skipOwaUrlCertificateValidation" value="false" />
 </appSettings>

  <connectionStrings />


 <casClientConfig
casServerLoginUrl="https://winserver.xtanki.local:8443/cas/login";
                 serverName="https://winserver.xtanki.local:8443";
                 secureUriRegex="(?i)/auth"

 casServerUrlPrefix="https://winserver.xtanki.local:8443/cas";
                 redirectAfterValidation="false"
                 useSession="false"
                 gateway="false"
                 renew="false"
                 ticketValidatorName="Cas20"
                 ticketTimeTolerance="5000"
                 singleSignOut="false"
                 proxyGrantingTicketReceptor="true"

 proxyCallbackUrl="https://winserver.xtanki.local/coa/proxyCallback";
                 proxyReceptorUrl="/coa/proxyCallback" />
_________________________________________________________________

Created a virtual directory in my IIS 6.0 on the Default Web Site tree with
the name "coa".
_________________________________________________________________

So now here's my questions:

1) The properties (authentication, httphandlers, etc) in the web.config file
supplied in the casowa zip, are to copy to the web.config file in the OWA
virtual directory? Or just leave it like that in the coa Virtual Directory?

They go in the coa virtual directory.  Nothing in casowa.zip goes into
OWA directory.


2) The property proxyCallbackUrl in casClientConfig bean.. what does it
mean? Its automatically created by the casowa client?

This the URL that CAS will use to authenticated and fulfill coa
requests for a ProxyTickets.


3) How do I test if clearPass is working? If i go to the address
https://winserver.xtanki.local:8443/cas/clearPass it redirects me to the
/login servlet..

See: http://www.unicon.net/blog/3/deploying_clearpass

You could also deploy the Java Client Simple WebApp Sample to ensure
ProxyTickets are working properly.
http://www.ja-sig.org/wiki/display/CASC/JA-SIG+Java+Client+Simple+WebApp+Sample


4) The Http HandlerMappins / Http Modules are supposed to be hardcoded into
the web.config file of owa? Where do I configure that in IIS 6??

Handlers and Modules are configured in Web.config either by hand or
using the IIS Manager:
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/b0c14479-83e3-435d-a935-819fe396e7d2.mspx?mfr=true


5) Whats the managed pipeline mode and How do I set it to Integrated?

Managed Pipeline mode is a new unified request processing pipeline
that is exposed to both native and managed components in IIS7.  Is is
not available on IIS6.
http://learn.iis.net/page.aspx/244/how-to-take-advantage-of-the-iis7-integrated-pipeline/

Hope this helps.

Cheers,
Bill

Thanks for your time,

Francisco



--
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