You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 349 Next »

Future Calls: Chose the ones (Wed. and/or Fri.) that works best for your schedule and time zone):

Wednesday, 23 May 2018, at 3 pm Eastern, Noon Pacific, 8 pm UTC

Friday 25 May 2018, at 10 am Eastern, 7 am Pacific, 3 pm London, 4 pm Amsterdam


We will be using ZOOM for web conferencing from now on

ZOOM  https://internet2.zoom.us/j/6785432100


√ Or by phone:  US: +1 646 558 8656  or +1 669 900 6833

Meeting ID: 678 543 2100    

International numbers available: https://zoom.us/u/d1DCOApkc

Or an H.323/SIP room system:

162.255.37.11 (US West)
162.255.36.11 (US East)
 221.122.88.195 (China)
115.114.131.7 (India)
213.19.144.110 (EMEA)
202.177.207.158 (Australia)
209.9.211.110 (Hong Kong)
64.211.144.160 (Brazil)
 69.174.57.160 (Canada)  

Meeting ID: 678 543 2100   

SIP: 6785432100@zoomcrc.com

Or Skype for Business (Lync):   https://internet2.zoom.us/skype/6785432100


Agenda and Collaborative scribing notes starting March 14, 2018 are HERE

Attendees are encouraged to participate in live-scribing the meetings on the above Google doc

Archive of older meeting notes:

  1. Up to March 9 2018 http://bit.ly/apiRegWG-6

  2. Up to Sept. 20 2017 http://j.mp/apiRegWG-5

  3. up to April 19 2017 http://bit.ly/tierApiReg

  4. up to 18 January 2017: http://j.mp/1PWMCp5

  5. From 4 November 2015 to 16 June 2016: https://tinyurl.com and links are also within the current document.

Email List: tier-api@internet2.edu 

  – To subscribe, browse to  https://lists.internet2.edu/sympa/subscribe/tier-api  

Working Group Chair: Keith Hazelton, University of Wisconsin

Charter for Data Structures and APIs Working Group

Inventory of TIER APIs

  • Credential Management (openapi)
    • Used to manage credentials for a Person or Entity
  • Group Registry (openapi)
    • Used for Group and Group Member related requests
    • SCIM (+ extensions?)
  • ID Match (openapi)
    • Used by Registry or SORs to obtain a Reference ID based on (SOR) attributes
  • Person Registry (openapi)
    • Used for Person (and maybe other Entity?) related API requests
    • SCIM (+ extensions)
  • Subscriber Message Notification (openapi)
    • Used to send update notifications to downstream systems

Other resources





See Also:

  • No labels