- Created by Albert Wu (internet2.edu), last modified on Feb 09, 2021
Jump to:
Overview
sn is a user attribute defined in RFC4519→ (Lightweight Directory Access Protocol (LDAP): Schema for User Applications). From RFC4519: "The sn (surname in X.500) attribute type contains name strings for the family names of a person."
Use in the InCommon Federation
sn is commonly used to transmit a person's last (family) name. Some IdPs may send multiple permutations of the person's name in the givenName attribute.
sn, in conjunction with givenName
, satisfies the REFEDS Research & Scholarship (R&S) entity category's requirement for person name.
SAML Response Example
<samlp:Response xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" ID="..." Version="2.0" IssueInstant="2020-07-17T01:01:48Z" Destination="...." InResponseTo="..."> ... <saml:Assertion ...> ... <saml:AttributeStatement> <saml:Attribute xmlns:x500="urn:oasis:names:tc:SAML:2.0:profiles:attribute:X500" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:uri" Name="urn:oid:2.5.4.4" FriendlyName="sn" x500:Encoding="LDAP"> <saml:AttributeValue xsi:type="xsd:string">El-Kabany</saml:AttributeValue> </saml:Attribute> ... </saml:AttributeStatement> </saml:Assertion> </samlp:Response>
See Also
Working with user data
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
Related content
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
Get help
Can't find what you are looking for?