Grouper Developers Forum

[Chris Hyzer <>]

Gary, thanks for organizing.  Here are responses from Penn, and I will be on 
the call on Wed.

> 1. what forms of "web services interface" ought to be in the core product
> in, say, the next 1 year?

You mean SOAP vs. REST?  Or which operations?  We would like SOAP and simple 
operations like add/edit groups, add/remove members (individually or in batch)

> 2. should SOAP be supported by the first WS-capable release (which *might*
> also have additional capabilities)?

Yes

> 3. what tools are most commonly used on campuses to create WS instances and
> their clients?

We use Axis SOAP, and handcoded REST (but prefer Axis since it does a lot of 
code generation)

> 4. what grouper-WS authentication and access control requirements do
> campuses have?

Our central authentication system does not currently support apps (only 
people), so anything is fine that has usernames/passwords.  E.g. let the app 
server or web server do http simple-auth.  However, we would like to be able 
to lock down a user with a source IP address or subnet.  Perhaps a table and 
maintenance screen that matches up a username with a source IP addresses or 
subnet


Thanks,
Chris