Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

eduPerson is a Lightweight Directory Access Protocol (LDAP) schema designed to include widely-used person and organizational attributes in higher education.

 

What is the aim of defining eduPerson attributes?

 

What is the relation of eduPerson to inetOrgPerson and other standards?

 

How can use of eduPersonAttributes protect users' privacy?

 

Are eduPerson attributes inteded or actually used (consumed) as LDAP attributes, or as attributes in SAML assertions? (Am I doing something I will regret if I build SAML attributes in the IdP from existing attributes in my campus LDAP/AD directory, for example building ePPN from sAMAccountName?)

 

Are theire canonical values of eduPersonAssurance that are or should be recoginzed by service providers?

 

If eduPerson directory attributes are multi-valued, can one assume services will be able to properly consume corresponding multi-valued SAML attributes?

Why does eduPerson include the eduPersonOrcid attribute and not eduPersonResearcherId? Won't this lead to new attributes for every kind of identifier?

...