CoSign and WebObjects
CoSign and WebObjects
- Subject: CoSign and WebObjects
- From: email@hidden
- Date: Wed, 23 Aug 2006 09:08:44 -0400
Date: Wed, 23 Aug 2006 09:04:24 -0400
Subject: CoSign and WebObjects
On Aug 22, 2006, at 9:24 PM, Q wrote:
On 23/08/2006, at 5:24 AM, Jonathan Maybaum wrote:
Because there continues to be discussion on the list about
GVC.SiteMaker and WO web-publishing apps, and how they compare, I
thought that I would provide a link to this presentation:
http://sitemaker.umich.edu/maybaum/files/usc-sitemaker.pdf
I think that this provides a bit more insight about what
GVC.SiteMaker (called UM.SiteMaker at the University of Michigan)
is all about.
Is the Cosign auth handling mentioned in this presentation managed
in the application or using an external module?
A little bit of both. Authentication is managed by mod_cosign
integrated into Apache. Cosign can be backed by different credential
stores, Kerberos is used in this case. Google cosign for the full
story. The app checks the REMOTE_USER HTTP header to get the
identity of the authenticated user and uses that for authorization
internally. The apps also redirects to HTTPS to force authentication
if an authenticated identity is not found.
I am interested in Cosign, but haven't looked into what is required
to use it with WO.
Very little. Just read that header and redirect to https if it is
not present.
Chuck
If folks are interested in CoSign, I'll be releasing in about six -
seven weeks some WO classes to simplify working with the system.
In the last two years we've placed three WO applications into
production. The platform still seems viable at Michigan.
Thanks,
Barry
--
Barry A Starrfield
Lead Analyst / Programmer
University Housing
University of Michigan at Ann Arbor
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden