I'm a little farther, I'm now at the point where I get the "HttpContext.Current.User is null" error but I read that they be due to an incorrect SSL certificate which our Exchange server has. I set the skip OWA cert parameter to false, but I don't know if that effects the CAS side of things.
Is there something I need to do on the CAS side of the setup to allow the process, or should a correct SSL cert do the trick? I'll find out tomorrow. -James On Nov 11, 2010, at 7:39 PM, "William G. Thompson, Jr." <[email protected]> wrote: > Did you follow these instructions? > https://wiki.jasig.org/pages/viewpage.action?pageId=29133913 > > Bill > > > On Thu, Nov 11, 2010 at 4:29 PM, James Winter <[email protected]> wrote: >> Some background: >> I setup the CAS Client for OWA on a test Exchange 2003 server in IIS 6 and I >> can successfully get to server.domain.local/coa/auth. I get redirected to >> the CAS login, which then redirects me back to >> server.domain.local/coa/auth?ticket=ST-XXX-xxxxetc which gives me a 404 >> error. >> Am I missing a configuration piece somewhere? Or does anyone know what the >> CasOwa.OwaUrl should be for Exchange 2003? I've tried /exchange, /exchweb, >> /exchweb/bin/auth, and a few others with no change. >> Thanks. >> -James >> >> -- >> 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
