Meeting Details: Tuesdays, 4:00 - 5:00 pm Eastern Time, 1:00 - 2:00 Pacific Time
Dial-in numbers:
+1-734-615-7474 (Please use if you do not pay for Long Distance),
+1-866-411-0013 (toll free US/Canada Only)
Access code: 0150432#
Participants
Who |
With |
Attending |
---|---|---|
Omer Almatary |
Rutgers University |
|
Rob Carter |
Duke University |
√ |
Celeste Copeland |
Univ. of North Carolina |
√ |
Warren Curry |
U Florida |
|
Michele Decker |
U of Notre Dame |
|
Tom Dopirak |
CMU |
√ |
Jeremy Grieshot |
Clemson University |
√ |
Keith Hazelton |
UW-Madison / Internet2 |
√ |
Karsten Huneycutt |
Univ. of North Carolina |
|
Steve Olshansky |
Internet2 |
|
Derek Owen |
U of Notre Dame |
|
Andrew Petro |
Unicon |
|
Chris Phillips |
Canarie, CA |
|
Gary Sharpe |
UC Davis |
|
Muhammad Siddique |
Rutgers University |
√ |
Bill Thompson |
Unicon / Jasig |
|
Boyd Wilson |
Clemson University |
√ |
AGENDA (See meeting notes for more detail)
- The Clemson University provisioning connector architecture (and possible use in CIFER) (Boyd Wilson)
- NetIQ XSLT might be more site specific vs. Scripts that know how to talk to specific endpoints are the more interesting shareable bits;
- Does need to have the concept of a filter, etc. Might have to build something to do a message bus version of this. Something that directs who cares about what.
- Synergy around ActiveMQ; Jeremy can look into that; Wiring to the bus; two layers to the discussion; If either CPR or OR put events on the bus, what's the common model? SCIM? SPML?
- The technology is more generic than person identity info provisioning
- Provisioning at Rutgers using Open Registry (Muhammad Siddique)
- Use CAMEL at both producer (of events) dB table of the queue. event type, person information; add person, update, add role,...
- Consumer listening on the queue and provisions to end points like legacy CTB? and LDAP.
- Roadmap: ActiveMQ with CAMEL endpoints
- CAMEL have about 70+ components, we're using several of them.
- Changelog dB table / Event log will continue on, but be supplemented
- Mix & match backend registries that we work with & see if the CAMEL; with OR after changelog gets created and rest could change; is that an interesting cleavage plane?
- Detailing the CIFER P&I three and six month work plan
- by January 31, 2013
- Use cases for demo solutions fully documented;
- UNC Improv provisioning
- Notre Dame provisioning
- PennState CPR provisioning
- Rutgers OR provisioning
- Clemson provisioning
- U Fl QuickReg Guest System
- UW-Madison PersonHub provisioning to O365 and to HR (Oracle/PS HCM)
- Duke U O365,...
- UC Davis
- ? Producing flat file batch reloads
- ? Downstream batch diff based provisioning
- ? Changelog processing model
- Toolkits identified
- P&I models documented and illustrated by reference to above
- Vetting emerging CIFER APIs against our P&I use cases
- NOTE: CIFER API calls are biweekly on Wednesdays at Noon Eastern, 9:00 am Pacific; the next call is November 14.
- Same conference call line as this call, with access code 0121717#
- Do we mix in CAMEL and ActiveMQ with REST? Persistence would be the challenge. Some way to match the Clemson transport with back-end storage
- Use cases for demo solutions fully documented;
- by April 30, 2013
- Demo solutions implemented and documented including recipes, tool choices and code snippets
- Detailed roadmap for P&I deliverables over following 12-18 months
- by January 31, 2013
NB: Omer Almatary and Muhammad Siddique will join a future CIFER-P&I call to detail Rutgers U approach to provisioning into Workforce.
Action Items:
[KeithH] Work with Clemson on detailing next steps
[RobC] Approach Omer, Muhammad, JimmyV about shared interest in ActiveMQ