FIFER API
DATE and TIME: May 26, 2011, 11:15 MDT
CONVENER: Benn Oshrin
SCRIBE:
# of ATTENDEES: 10
MAIN ISSUES DISCUSSED
FIFER API documentation is housed on JASIG wiki:
https://wiki.jasig.org/display/FIFER/Home
https://wiki.jasig.org/display/FIFER/API
****************************
- What do we mean by API?
- goal to make it easy for developers to build deploy apps using this
- looking for some lib API to drop in and configuration
- not make life more difficult for server admins either
- goal to make it easy for developers to build deploy apps using this
- FIFER is a community of practice - team of folks that may not necessarily implement code
- Multiple types of APIS needed for FIFER
- How do we standardize provisioning connectors
- different SPs may have different provisioning needs/impls
- Discussed outline thus far - see wiki above)
- group objects w/in the FIFER API
- group operations interfaces, hasMember(...), hasMembers(...), getMemebers(...), getGroupsForMember(...), etc.
- generally covered current state of groups API
- Group Web Service Demo approach
- not currently RESTful interface, but not working POC yet.
- if we need to worry about wire protoocl, YES - then we should provide RESTful approach - as it may be seen as easier to adopt
- others may simply prefer SOAP bindings or REST + SOAP
- alternatively - use Apache Thrift - get bindings and wire protocol
- Noted that diagram showed GROUPer leveraged in the map.
- given this why not leverage all Grouper APIS - Benn suggested that FIFER may not need such a large set of APIs
- confirmed FIFER isn't just about Groups
ACTIVITIES GOING FORWARD / NEXT STEPS
- Need to figure out best way to move forward WRT preferred approach for Group Web Service aka Alternate Demo Plan Mock-ups
- FIFER needs project player (FIFER API consumer) input, but also those in VO/CO space
If slides are used in the session, please ask presenters to convert their slides to PDF and email them to SteveO@internet2.edu
Thank you!