SAML attribute naming

[Tom Poage]

On 10/17/2014 09:08 AM, Peter Schober wrote:
> The page name even matches the subject from your post :)
> https://wiki.shibboleth.net/confluence/display/SHIB2/AttributeNaming
> 
> * Eric Goodman <Eric.Goodman at ucop.edu> [2014-10-17 18:00]:
>> I'm currently working with a vendor that is asking for attributes
>> with names (not friendly names) such as "firstname", "lastname",
...
> URI (not URN specifically) naming avoids that by using globally unique
> names, which also reference the source of the definition uniquely.
> So both parties can be sure of the syntax and semantics via reference
> to an existing, external standard.
> -peter

Right. That didn't stop e.g. Salesforce from doing things their own way,
making more work for all of us, instead of leveraging standards or
convention:

> <resolver:AttributeDefinition xsi:type="ad:Simple" id="User.Username" sourceAttributeID="eduPersonPrincipalName">
> <resolver:AttributeDefinition xsi:type="ad:Simple" id="User.LastName" sourceAttributeID="sn">
> <resolver:AttributeDefinition xsi:type="ad:Simple" id="User.FirstName" sourceAttributeID="givenName">
> <resolver:AttributeDefinition xsi:type="ad:Simple" id="User.Email" sourceAttributeID="mail">

"No Software." It's replaced by configuration instead.

Tom.