COmanage Developers List

[Tom Barton <>]

[reducing the # of lists CCd]

Grouper (and eventually, signet) web services are perhaps more likely to 
be of value to the tools integrated into comanage. Ie, some may get 
their group & priv info from ldap, but others may more appropriately do 
so via WS. To make this concrete, consider Newcastle's use of web 
services in a 404 screen that enables a user whose access to protected 
content was just rejected, to enroll for access. That's a tool-grouper 
interaction mediated by web services.

Tom

Scotty Logan wrote:
> On Apr 23, 2008, at 10:52 PM, Chris Hyzer wrote:
> > Im interested in the comanage deployment architecture… I tried to look 
> > at documentation and presentations… anyways, are signet and grouper 
> > UIs in separate warfiles (classloaders)?
>
> Yes, they are / will be in separate warfiles.
>
> > Are there plans to deploy grouper/signet web services to comanage, and 
> > if so will those be in separate webapps from the ui (i.e. 4+ webapps)?
>
> CoManage only supports Shibboleth for authentication, so support for web 
> services is complicated.  Having said that, all the infrastructure to 
> support web services and alternative service to service authN is already 
> there within CoManage, but it's outside the current scope (IMHO).
begin:vcard
fn:Tom Barton
n:Barton;Tom
org:University of Chicago;Networking Services & Information Technology
adr;dom:1155 E. 60th St.;;Rm 309, 1155 Bldg;Chicago;IL;60637
email;internet:
title:Sr. Director - Integration
tel;work:+1 773 834 1700
version:2.1
end:vcard