Gateway | Attribute Mappings

The Cirrus Gateway maps the attributes returned by each of the Social Providers to appropriate eduPerson attributes. The tables below outlines the current mapping.

Google

Attribute SAML/MACE Dir Attribute
given_name givenName
family_name sn
email mail
sub@google.com or email eduPersonPrincipalName

Facebook [3]

Attribute SAML/MACE Dir Attribute
first_name givenName
last_name sn
name cn
id@facebook.com [1] eduPersonPrincipalName

Microsoft

Attribute SAML/MACE Dir Attribute
first_name givenName
last_name sn
name cn
mail['account'] mail
id@live.com eduPersonPrincipalName

LinkedIn [3]

Attribute SAML/MACE Dir Attribute
firstName givenName
lastName sn
id@linkedin.com [2] eduPersonPrincipalName

Yahoo!

Attribute SAML/MACE Dir Attribute
http: //axschema.org/namePerson displayName
http: //axschema.org/contact/email mail
http: //axschema.org/contact/email eduPersonPrincipalName

Twitter [3]

Attribute SAML/MACE Dir Attribute
name cn
screen_name displayName
id@twitter.com eduPersonPrincipalName

Weibo

Attribute SAML/MACE Dir Attribute
name cn
screen_name displayName
id@weibo.com eduPersonPrincipalName

  1. Facebook IDs are tied to the API key used for integration. If a consistent ID is desired, the same API key must be used for each integration.

  2. LinkedIn IDs are tied to the API key used for integration. If a consistent ID is desired, the same API key must be used for each integration. A LinkedIn ID is mixed case, alphanumeric and can also contain '-','_' and possibly '='.

  3. Facebook, LinkedIn, and Twitter can be configured to return the primary email address. This however can be changed by the user at any time and should not be considered a persistent attribute.