LDAP Options, Subtrees and Composite attributes for Identity
DATE and TIME: Friday 26 May 2001, 10:00 - 11:00 am
CONVENER: Roland Hedberg, Michael Gettes
SCRIBE: Keith Hazelton
# of ATTENDEES: 10
Attendee | Institution |
---|---|
Roland Hedberg | Umea University |
Benn Oshrin | Internet2 Middleware |
Todd Piket | UMN |
Michael Gettes | CMU |
Billy Cook | Clemson U |
Jeremy Grieshop | Clemson U |
Jim Green | Michigan State |
Michael Pelikan | Penn State |
Emily Eisbruch | Internet2 |
Keith Hazelton | UW-Madison |
MAIN ISSUES DISCUSSED
Take email address: (the "attribute option" specifies the intended use or purpose of each value of email address)
...
SUMMARY FROM REPORT OUT TO THE LARGER GROUP : Multiple approaches for handling structured data in LDAP, including composite attributes. OpenLDAP v. 389 v. others, and comparisons will be written up for reference...
ACTIVITIES GOING FORWARD / NEXT STEPS
\[ACAMPScribe:Todd Piket\] Send writeup of issue statement for eP\{Scoped\}PAunmigrated-wiki-markup Wiki Markup
\[ACAMPScribe:Roland, MichaelG, Keith\] Writeup The Options: 1) Why would you ever want to do this in LDAP? attr. options, composite attributes, sub-entries, ... Start with use cases. Bake-off.
\[ACAMPScribe:Keith\] Ask Rob Carter for permission to use the 389DS plugin that he & Michael Gettes wrote to handle Kerberos "the right way". Wiki Markup
REQUESTS
RESOURCES