Grouper Developers Forum

["GW Brown, Information Systems and Computing" <>]

Apologies for the late posting. I have attached an HTML table which 
summarises the responses, so far, to the questions I posted to the list on 
Monday. I hope I haven`t mis-represented any one. more responses very 
welcome.

Gary

--On 27 November 2007 13:24 -0500 Jessica Bibbee <> 
wrote:

> Hello Folks,
>
> Please join us for the Grouper Working Group call tomorrow, Wednesday,
> 28-Nov at 12:00 EST.
>
> The agenda and bridge info is below.
>
> Thanks! Jessica
>
>
>
> *************************************************************************
> **
>
> Wednesday, 28 November 2007, 1200EST (1700Z), 60 minutes
>
>          +1-866-411-0013 (toll free US/Canada Only), or
>          +1-800-392-6130 (alternate toll free US/Canada Only)
>         +1-734-615-7474 (Non-US/CA, non-toll free, no dialout)
>           http://edial.internet2.edu/call/0109331 for SIP
>           PIN: 0109331 (followed by "#")
>
> Agenda:
>
> 1. administrivia
>       . <http://www.internet2.edu/membership/ip.html>
>       . agenda bash
>       . approve minutes
>      . review AIs
>       . next meeting
>
> 2. v1.2.1 Status / v1.2.1 RC1 Released
>
> 3. Grouper & Web Services
>
>   . What forms of "web services interface" ought to be in the core
> product in, say, the next 1 year?
>   . Should SOAP be supported by the first WS-capable release (which
> *might* also have additional capabilities)?
>   . What tools are most commonly used on campuses to create WS instances
> and their clients?
>   . What grouper-WS authentication and access control requirements do
> campuses have?
>
> 4. adopt-an-agenda
>
> --
> Jessica Bibbee, Technical Analyst
> Internet2
>
> mobile: +1-734-255-6644
>
> The Internet2 Dynamic Circuit Network:
> Unleash your Interdomain Imagination
> http://www.internet2.edu/network/dc/



----------------------
GW Brown, Information Systems and Computing

Title: Untitled Document

Grouper & Web Services - summary of responses

1. What forms of "web services interface" ought to be in the core
Penn	Simple and batched operations e.g. add/edit groups, add/remove members using SOAP
Cornell	??? Similar to Penn? Limited number of operations available using SOAP
Washington	Full API available preferably via REST
gFIVO	Strongly typed JAX-WS
GridGrouper	Full API via SOAP
2. Should SOAP be supported by the first WS-capable release (which *might* also have additional capabilities)?
Penn	Yes
Cornell	Yes, but will be investigating REST
Washington	REST preferred, as I mentioned. If SOAP is to be supported it would be important IMHO to clarify a development plan (eg write WSDL based on current APIs, import into various identified SOAP toolkits, test with various client languages etc) to make sure we're on the same page regarding methodology and benefits.
gFIVO	Yes. Also interested in using REST along side SOAP
GridGrouper	Yes
3. What tools are most commonly used on campuses to create WS instances and their clients?
Penn	We use Axis SOAP*, and handcoded REST. *preferred due to code generation
Cornell	Axis SOAP. .jws on the server side and generate stubs on the client side via Axis wsdl2java class.
Washington	People are writing support for REST interfaces in Java, Perl, Ruby, etc. WS-* interfaces I'm aware of have been MS tools on the server side, and MS and homegrown on the client side.
gFIVO	WSO2 Web Services Application Server (WSAS) in tandem with the Eclipse Web Tools Platform (WTP) Project using WTP 2.0 drivers. Provides Axis 1/2 support + client generation in many languages.
GridGrouper	Globus / Axis / Introduce
4. What grouper-WS authentication and access control requirements do campuses have?
Penn	http simple-auth via the app server or web server. Would like to restrict specific users by IP/subnet
Cornell	Ideally WS-Security, but in practice container authentication. Concerned about Axis 2 and use of HttpClient
Washington	Container-based. Need to deal with process and user authentication
gFIVO	IP and username/password (via container?). Would like to use WS-Security
GridGrouper	PKI