Protocols/MSNP/Activities/SDK/Techref/Flags/UserProperties: Difference between revisions
Animadoria (talk | contribs) (Created automatically by Anima Importer) |
Animadoria (talk | contribs) (Created automatically by Anima Importer) |
||
| Line 1: | Line 1: | ||
<!-- Generated @ 08/12/2022 23: | <!-- Generated @ 08/12/2022 23:45:49 +01:00 using Anima's CHM converter based on techref/flags/UserProperties.htm --> | ||
{{Protocols/MSNP|section=Activities}} | {{Protocols/MSNP|section=Activities}} | ||
__NOTOC__= Permission Flags - UserProperties = | __NOTOC__= Permission Flags - UserProperties = | ||
Revision as of 22:45, 12 August 2022
Permission Flags - UserProperties
If an application has the UserProperties flag enabled in the MSN® Messenger Activity directory, three additional properties are available in the User object: EMail, Name, and PUID. Unlike the PassportSiteID permission flag, however, this flag does not cause the Messenger client to perform a Microsoft® .NET Passport authentication when the application loads.
By accessing these properties, an application can get the e-mail address, user name, and .NET Passport Unique ID (PUID) of the .NET Passport used to sign in.
Note To help protect user privacy, if your application uses this feature, you must notify the user that your program will access personal information. This notification must state exactly what information will be accessed (e-mail address, user name, PUID, or IP address), and must give the user an opportunity to cancel before the information is accessed.
To be considered a candidate for this permission flag, an application must demonstrate a need for the ability to access the e-mail address, user name, PUID, or IP address of the local user, and must comply with the privacy requirements just described.
This permission flag might be useful for an application sending e-mail to the local or remote participant or for uniquely identifying a user by PUID.