Jump to: 


eduPersonPrincipalName (eppn) is a user identifier attribute defined in the eduPerson→ LDAP object class. It is a scoped identifier for a person. As this identifier is often used by humans to identify the person it represents, ePPN values are often, but not required to be, human-friendly, and may change as a result of various business processes.

LDAP Syntax

Directory String

# of Valuesmulti-valued

Use in the InCommon Federation

eppn is supported in the InCommon Federation. It is widely used in InCommon as well as in global R&E federations.

eppn satisfies the REFEDS Research & Scholarship (R&S) entity category's requirement for a shared user identifier if it is non-assigned. If an eppn can be re-assigned, it must be sent along with eduPersonTargetedID to satisfy R&S's requirement for shard user identifier.  

IMPORTANT: an eppn is not an email address.

While an eppn's format appears similar to that of an email address, implementors MUST NOT assume that an eppn is a routable email address. If a service requires a user's email address, it MUST request it via a separate mail attribute. 

SAML Response Example

<samlp:Response xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"         
                ID="..." Version="2.0" IssueInstant="2020-07-17T01:01:48Z" 
                Destination="...." InResponseTo="...">
 <saml:Assertion ...>
    <saml:Attribute xmlns:x500="urn:oasis:names:tc:SAML:2.0:profiles:attribute:X500"
      <saml:AttributeValue xsi:type="xsd:string">mjc@example.edu</saml:AttributeValue>

See Also