I'd like to see a relatively generic solution that can handle OWA, as well as other applications that can't easily integrate with CAS. At that point, if you were not using an intermediary such as uPortal, you could build a module onto CAS that recognized particular URLs and would submit credentials to those URLs (possibly tied to the Services Management tool?)
On Tue, Dec 1, 2009 at 9:23 PM, William G. Thompson, Jr. <[email protected]>wrote: > Folks, > > I'm wondering if a potential solution for the OWA SSO problem might be > to create a custom OWA CAS client. The idea is inspired by the Martin > Norrsken solution and the CASifying Outlook Web Access 2 work by > Matthieu MARC. Both of these solution rely on the CAS server to > replay credentials to OWA and snarf the session cookies for the > browser. > > With ClearPass we could move this get-the-owa-session-cookie-logic to > the OWA host. The OWA CAS Client would request the password from CAS, > replay to owa in the background, capture the owa session cookies, set > them on the browser (with the benefit of coming from the OWA host), > and redirect to owa mailbox. > > I'd be grateful for any thoughts, insights, etc... > > Thanks, > Bill > > -- > 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
