Hi,

I haven't looked at Bill's CASOWA code yet.  It looks like it's a Web
Application Project which means you'd have to open the CasOwa.csproj and
build it.  That would create a coa/bin directory with CasOwa.dll and I
think DotNetCasClient.dll.   

Also, you wanted to use 'Add Application', not 'Add Virtual Directory'
in IIS.  The Virtual Directory will only support static content, whereas
the Application will allow ASP.NET code to run.

I'm not sure about the web.config/authentication stuff.  Windows
authentication and Forms authentication are 2 different things.  I'm
pretty sure that the web.config needs to be configured to work with
DotNetCasClient.dll, not Outlook Web Access so you'd probably want to
revert that change.  As I understand it, Bill's code authenticates the
user with CAS, pulls the password via ClearPass, logs into the Exchange
server using those credentials, and redirects you to your inbox.

Good luck.

-ScottH

> -----Original Message-----
> From: Cary, Kim [mailto:[email protected]]
> Sent: Thursday, May 27, 2010 2:22 PM
> To: [email protected]
> Subject: Re: coa/auth not redirecting Re: [cas-user] CAS ClearPass
> Outlook .NETCASClient integration on IIS 7
> 
> Scott,
> 
> Thanks for your reply.
> 
> We've basically unpacked Bill's github COA distribution into a
> directory on our webmail server and added its top level directory
> (c:\coa) to the IIS running webmail as a virtual directory /coa. We
can
> access c:/coa/license.txt as https://webmail.../coa/license.txt
> 
> Then, we edited web.config for our local environment (i.e. choose
> windows forms authentication, since that is what OWA uses and fill
out
> the URL for our CAS server.
> 
> I'm hoping, since we didn't write this application or create the
> distribution folder that we don't have to check namespaces and such in
> the C# application files and aspx (this project works as-is for
others,
> but our environment IIS7/2008/EXCH2007 seems unique maybe, hence the
> existing walkthru's don't work for us).
> 
> Only 2 files? Here's what we've got in c:\coa:
> 
> /coa:
> CasOwa.csproj                 Properties/
> CasOwaAuthHandler.cs          Web.config
> Default.aspx                  lib/
> Default.aspx.cs                       license.txt
> Default.aspx.designer.cs
> 
> /coa/Properties:
> AssemblyInfo.cs
> 
> /coa/lib:
> DotNetCasClient.dll
> 
> Is it possible we've made the wrong choice with web application
> project?
> 
> Should we try the 'convert to web application' or somehow go back to
> being a web site?
> 
> Thanks again,
> KC
> 
> On May 27, 2010, at 7:10 AM, Scott M. Holodak wrote:
> 
> > Hi Kim,
> >
> > It looks like you're using a Web Application Project as opposed to a
> > website.  A few things to check:
> >
> > - Make sure that you've built the web application.  This can
> sometimes
> > happen when the page you're browsing to hasn't been compiled yet.
> >
> > - Make sure your namespaces and class names match in all 3 files
(see
> > below).
> >
> > - If you've converted from a web site to a web application & you
only
> > have 2 files (Default.aspx and Default.aspx.cs), right click on
> > Default.aspx and click 'Convert to web application'. Then rebuild.
> >
> > - If you're trying to point IIS to the web application root as
> opposed
> > to publishing the application somewhere, make sure that your Bin
> > directory contains all of the project dlls and they are up-to-date
> (in
> > the bin directory itself, not subdirectories).  If you're explicitly
> > targeting x86 or x64, you might need to copy these files from
> > bin\x86\debug to bin\.  I usually do this in a Post Build Event:
> "copy
> > $(TargetPath) $(ProjectDir)bin\".
> >
> > -ScottH
> >
> > ============
> > Default.aspx
> > ============
> > <%@ Page Language="C#" CodeBehind="Default.aspx.cs"
> > Inherits="CasOwa._Default" %>
> >
> > ===============
> > Default.aspx.cs
> > ===============
> > ...
> > namespace CasOwa
> > {
> >    public partial class _Default : System.Web.UI.Page
> >    {
> > ...
> >    }
> > }
> >
> > ========================
> > Default.aspx.designer.cs
> > ========================
> > ...
> > namespace CasOwa
> > {
> >    public partial class _Default
> >    {
> > ...
> >    }
> > }
> >
> >
> >> -----Original Message-----
> >> From: Cary, Kim [mailto:[email protected]]
> >> Sent: Wednesday, May 26, 2010 2:43 PM
> >> To: [email protected]
> >> Cc: Scott M. Holodak
> >> Subject: Re: coa/auth not redirecting Re: [cas-user] CAS ClearPass
> >> Outlook .NETCASClient integration on IIS 7
> >>
> >> All right, we've determined we're running in "Integrated Mode".
> >>
> >> I believe the web config is correct (attached) - can someone look
at
> > it
> >> to verify or suggest another approach to determining the problem?
> >>
> >> The error we're getting is:
> >> Server Error in '/coa' Application.
> >> An error occurred during the parsing of a resource required to
> service
> >> this request...
> >> "Parser Error Message: Could not load type 'CasOwa._Default'.
> >> Source Error:
> >> Line 1: <%@ Page Language="C#" AutoEventWireup="true"
> >> CodeBehind="Default.aspx.cs" Inherits="CasOwa._Default" %>
> >> Line 2:
> >> Line 3: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
> Transitional//EN"
> >> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
> >> Source File: /coa/default.aspx
> >>
> >>
> >>
> >> --
> >> 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