...
Provider | First Name | Last Name | Transient Email* | Persistent Email | Human-readable Unique ID | Machine-readable Unique ID | SP-specific ID | ||
---|---|---|---|---|---|---|---|---|---|
| | |
| |
| (Have not verified this yet.) | (Have not verified this yet.) | ||
Google OAuth | | |
| | (Email...) | (Appears user can only look it up if Google+ is enabled for the account.) |
| ||
Google OpenID | | |
| | (Email...) |
| (The OpenID can either be set for the SP realm, or the domain realm, so only SP-specific if you ask Google to do that for you.) | ||
| |
|
| (Only if enabled via the Public Profile Settings page, however, a user can change this at will.) | | ||||
| |
|
| |
| (Have not verified this yet.) | (Have not verified this yet.) | ||
Windows Live | | | |
|
|
| (Email, but there is more than one, so perhaps not...) | (Have not verified this yet.) | (Have not verified this yet.) |
Info | ||
---|---|---|
| ||
* Unless the email address ends in the domain of the provider, then the likelihood that the the user can change at their whim is pretty high. This is great if you are using email as email, i.e., you want to actually know the user's email address. On the other hand, this can have very significant impacts on your service if you are trying to use email as the basis for eduPersonPrincipalName. |