COmanage Developers List

[Tom Barton <>]

First, grouper web services expose RESTful interfaces as well as 
SOAP-based ones. I think Newcastle has demonstrated their utility for 
php clients.

Second, if you do go for a CLI-based approach, I'm curious what gsh 
lacks that would motivate you to write another CLI to grouper. Could you 
guys report out about that?

Third, you can use gsh to read the database too, of course, so perhaps 
you don't need to deal with the phasing issues inherent in a read-LDAP 
write-grouper approach.

Longer term (and maybe even short term), I'd think grouper's REST 
interfaces are the way to go. Your feedback about any gap between what 
they offer and what you need would be very valuable for the project.

Thanks,
Tom

Digant C Kasundra wrote:
> (cc'ed comanage-dev b/c really, why not?)
>
> As an addendum to this, I just talked to Scotty who is going to write a 
> simple CLI tool in java that will use the java api and expose some simple 
> features that the php pages can call as execs.  Should work fine in the short 
> term.
>
>
> ----- "Digant C Kasundra" 
> <>
>  wrote:
>
> > Hey Tom,
> >
> > So I'm trying to come up with a sensible and doable approach to a
> > grouper dashboard for COmanage (something i can finish by end of this
> > week).  It seems that there is a Java API and then there is gsh. 
> > There is also a web services API but as far as PHP making calls that
> > too is probably not a workable approach.  I want to outline what I
> > think i will do this week but want to talk to you about what the best
> > long term solution is:
> >
> > Temporarily, I will have the php generate files to feed to gsh and
> > make changes to and query changes from Grouper.  The PHP will rely on
> > LDAP to get the list of users but will have to rely on gsh for all
> > else because until ldappc has run, the data will out of sync.
> >
> > Long term, I would imagine i would want something in the form of
> > RESTful alls or just php functions that I can call to make and query
> > Grouper.  Is there a good way for me to approach that?  gsh just seems
> > to be a wrapper around the java api calls but doing the same for php
> > would not be sensible.  Would php functions have to simply manipulate
> > the database directly?  (In which case it would be an actual tightly
> > coupled API that needs to stay current with changes to Grouper and the
> > storage of groups data.)  Looking for your advice in this area.
> >
> > --
> > Digant C Kasundra 
> > <>
> > Technical Lead, ITS Unix Systems and Applications, Stanford University