The only thing that runs on IIS Server is the CasOwa service. The CAS
server can be remote, I only installed on the same machine for
development purposes.
I'm finishing the wiki page to share my experience in casifying OWA.
Francisco
Andrew Tillinghast wrote:
Am I correct in understanding that the .NET CASOWA solution requires that the
CAS service is running on an IIS server?
-Andrew
On Mar 29, 2010, at 10:32 PM, Francisco Estanqueiro wrote:
Hi,
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/cas-user@lists.jasig.org/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?
2) The property proxyCallbackUrl in casClientConfig bean.. what does it mean?
Its automatically created by the casowa client?
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..
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??
5) Whats the managed pipeline mode and How do I set it to Integrated?
Thanks for your time,
Francisco
--
You are currently subscribed to cas-user@lists.jasig.org as:
atill...@conncoll.edu
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
--
You are currently subscribed to cas-user@lists.jasig.org as:
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
