Identity/Profile/Proposal - Revision history

Stomlinson: /* Comparisons */

2012-05-22T10:53:22Z

Comparisons

← Older revision		Revision as of 10:53, 22 May 2012
Line 36:		Line 36:
	id, name, first_name, middle_name, last_name, gender, locale, link (profile URL), username, cover (photo)		id, name, first_name, middle_name, last_name, gender, locale, link (profile URL), username, cover (photo)

	~~Persona would operate in a similar fashion~~. ~~Name and photo may be given by default, additional fields must be explicitly~~ requested.		OAuth suffers from an all or nothing approach to authorization. A user is unable to approve only a subset of the requested data.

	~~OAuth suffers from~~ an ~~all or nothing approach to authorization~~. ~~A user is unable to approve only a subset of the~~ requested ~~data~~.		Persona will operate using an explicit request/scope model, but give the user finer control over which fields are authorized. Name and photo may be given by default, additional fields must be explicitly requested.

	# - Facebook Connect - https://developers.facebook.com/docs/guides/web/#login		# - Facebook Connect - https://developers.facebook.com/docs/guides/web/#login

Stomlinson: /* Comparisons */

2012-05-22T10:51:48Z

Comparisons

@@ Line 26: / Line 26: @@
 == Comparisons ==
-Facebook Connect and OAuth?
+Facebook Connect[1] and OAuth[2] are two similar projects with similar aims. Facebook Connect is based on OAuth2.  While many sites such as Twitter use OAuth for authentication, it's original purpose is authorization.
 == User Data ==

Stomlinson: /* Background Bugs & Wiki Pages */

2012-05-18T13:02:00Z

Background Bugs & Wiki Pages

← Older revision		Revision as of 13:02, 18 May 2012
Line 55:		Line 55:
	* https://github.com/mozilla/browserid/issues/1588		* https://github.com/mozilla/browserid/issues/1588
	* https://github.com/mozilla/browserid/issues/1589		* https://github.com/mozilla/browserid/issues/1589
			* https://bugzilla.mozilla.org/show_bug.cgi?id=755732 - Legal for TOS/PP update
			* https://bugzilla.mozilla.org/show_bug.cgi?id=756431 - Security Review request

Stomlinson at 13:33, 16 May 2012

2012-05-16T13:33:42Z

← Older revision		Revision as of 13:33, 16 May 2012
Line 1:		Line 1:
	#Profile		= Profile =
	Adding Profile Data to Persona		Adding Profile Data to Persona

	##Background & Motivation:		== Background & Motivation ==
	Two of Persona's primary goals are to make signing up and signing into sites as easy as possible. Persona succeeds in making signin easy, but misses the mark for sign up. To create an account, many sites that use Persona must still ask users for additional personal information. How many times do users have to fill out their real names whenever they visit a new site?		Two of Persona's primary goals are to make signing up and signing into sites as easy as possible. Persona succeeds in making signin easy, but misses the mark for sign up. To create an account, many sites that use Persona must still ask users for additional personal information. How many times do users have to fill out their real names whenever they visit a new site?

Line 8:		Line 8:
	There should be a better way.		There should be a better way.

	##Proposal		== Proposal ==
	Add basic profile information to Persona. To make use of profile facilities, sites must request a set of profile information from a well defined list of possible attributes. Users would then have the opportunity to approve or deny the request, as well as modify any information that is released. Sites can request the data they need, users retain control over what is released.		Add basic profile information to Persona. To make use of profile facilities, sites must request a set of profile information from a well defined list of possible attributes. Users would then have the opportunity to approve or deny the request, as well as modify any information that is released. Sites can request the data they need, users retain control over what is released.

Line 18:		Line 18:
	Once key-wrapping support is ready, a profile server will be set up to save data and provide a sync mechanism across multiple devices. All data stored on the profile server will be client side encrypted much in the same way as Firefox Sync operates today. Keys to unencrypt the stored data will not leave the user's devices, making the data unaccessible to third parties who have access to Persona's servers.		Once key-wrapping support is ready, a profile server will be set up to save data and provide a sync mechanism across multiple devices. All data stored on the profile server will be client side encrypted much in the same way as Firefox Sync operates today. Keys to unencrypt the stored data will not leave the user's devices, making the data unaccessible to third parties who have access to Persona's servers.

	##Data collected		== Data collected ==
	Initially, only a minimal set of data will be requested from the user. The attributes collected are name and photo. In the future, additional attributes will be stored in multiple "contact cards". Additional data likely includes address, phone number, D.O.B., a web site, twitter handle, facebook handle, and possibly a short bio. The exact list of extended attributes which are collected have yet to be determined.		Initially, only a minimal set of data will be requested from the user. The attributes collected are name and photo. In the future, additional attributes will be stored in multiple "contact cards". Additional data likely includes address, phone number, D.O.B., a web site, twitter handle, facebook handle, and possibly a short bio. The exact list of extended attributes which are collected have yet to be determined.

	##Data retention		== Data retention ==
	Until key wrapping support is ready, profile data will be retained only on the user's device. When a user manually signs out of Persona or a new user signs in on the device, the original user's profile data will be cleared.		Until key wrapping support is ready, profile data will be retained only on the user's device. When a user manually signs out of Persona or a new user signs in on the device, the original user's profile data will be cleared.
	When key wrapping support is complete and client side encryption is possible, a profile server will be set up which acts as a sync mechanism. This data will be retained on Mozilla's servers but will be unaccessible by ourselves or by third parties as the keys to unencrypt the data will not leave the user's devices.		When key wrapping support is complete and client side encryption is possible, a profile server will be set up which acts as a sync mechanism. This data will be retained on Mozilla's servers but will be unaccessible by ourselves or by third parties as the keys to unencrypt the data will not leave the user's devices.

	##Comparisons		== Comparisons ==
	Facebook Connect and OAuth?		Facebook Connect and OAuth?

	##User Data		== User Data ==
	Concrete user data that will initially be collected:		Concrete user data that will initially be collected:

Line 36:		Line 36:
	}		}

	##Users affected		== Users affected ==
	All Persona users will be affected by this proposal. Approximately 100,000 sign-ins/month.		All Persona users will be affected by this proposal. Approximately 100,000 sign-ins/month.

	##Opt-in/Opt-out		== Opt-in/Opt-out ==
	All features will be opt-in. Users will not have to supply profile information. When sites request information, users can decline the request or modify any data before it is sent.		All features will be opt-in. Users will not have to supply profile information. When sites request information, users can decline the request or modify any data before it is sent.

	##Privacy Policy		== Privacy Policy ==
	Profile data collection and release may require a privacy policy update. Changes to our privacy policy will be made and published before this service is released.		Profile data collection and release may require a privacy policy update. Changes to our privacy policy will be made and published before this service is released.
	Profile information that a user releases to a site will be governed by that site's privacy policy and TOS.		Profile information that a user releases to a site will be governed by that site's privacy policy and TOS.

	##Publication of Collected Data		== Publication of Collected Data ==
	An individual user's profile data will never be published by Mozilla. We may publish aggregate information relating the number of users using the service or KPI indicators.		An individual user's profile data will never be published by Mozilla. We may publish aggregate information relating the number of users using the service or KPI indicators.

	Profile information that a user releases to a site will be published at that site's discression.		Profile information that a user releases to a site will be published at that site's discression.

	##Background Bugs & Wiki Pages##		== Background Bugs & Wiki Pages ==
	* https://github.com/mozilla/browserid/issues/880		* https://github.com/mozilla/browserid/issues/880
	* https://github.com/mozilla/browserid/issues/1588		* https://github.com/mozilla/browserid/issues/1588
	* https://github.com/mozilla/browserid/issues/1589		* https://github.com/mozilla/browserid/issues/1589

Stomlinson at 13:28, 16 May 2012

2012-05-16T13:28:51Z

← Older revision		Revision as of 13:28, 16 May 2012
Line 51:		Line 51:
	Profile information that a user releases to a site will be published at that site's discression.		Profile information that a user releases to a site will be published at that site's discression.

	##Background Bugs & Wiki Pages		##Background Bugs & Wiki Pages##
	https://github.com/mozilla/browserid/issues/880		* https://github.com/mozilla/browserid/issues/880
	https://github.com/mozilla/browserid/issues/1588		* https://github.com/mozilla/browserid/issues/1588
	https://github.com/mozilla/browserid/issues/1589		* https://github.com/mozilla/browserid/issues/1589

Stomlinson at 13:04, 16 May 2012

2012-05-16T13:04:25Z

← Older revision		Revision as of 13:04, 16 May 2012
Line 52:		Line 52:

	##Background Bugs & Wiki Pages		##Background Bugs & Wiki Pages
			https://github.com/mozilla/browserid/issues/880
			https://github.com/mozilla/browserid/issues/1588
			https://github.com/mozilla/browserid/issues/1589

Stomlinson: Created page with "#Profile Adding Profile Data to Persona ##Background & Motivation: Two of Persona's primary goals are to make signing up and signing into sites as easy as possible. Persona succ..."

2012-05-16T12:47:30Z

Created page with "#Profile Adding Profile Data to Persona ##Background & Motivation: Two of Persona's primary goals are to make signing up and signing into sites as easy as possible. Persona succ..."

New page

#Profile
Adding Profile Data to Persona

##Background & Motivation:
Two of Persona's primary goals are to make signing up and signing into sites as easy as possible. Persona succeeds in making signin easy, but misses the mark for sign up. To create an account, many sites that use Persona must still ask users for additional personal information. How many times do users have to fill out their real names whenever they visit a new site?

Services like Facebook Connect and OAuth make it easy for users to create a single profile that they can share with multiple sites, but these systems do not offer the user fine enough control over which data is released to which site. Users either give up everything or nothing.
There should be a better way.

##Proposal
Add basic profile information to Persona. To make use of profile facilities, sites must request a set of profile information from a well defined list of possible attributes. Users would then have the opportunity to approve or deny the request, as well as modify any information that is released. Sites can request the data they need, users retain control over what is released.

Initial plans are to collect only a minimal set of data - starting with name and photo. If a user fills in these two attributes, sites may get this data without explicit user consent - this detail has not yet been finalized.
Data will only be stored in localStorage on the user's browser until key-wrapping facilities are ready - there will be no initial server side component.

Once we better understand the needs of sites as well as the expectations of users, additional information will be collected in the form of "contact cards" A contact card is an individual profile, a user may have one contact card per email address. Additional fields in a contact card will likely include address, phone number, D.O.B., a web site, twitter handle, facebook handle, and possibly a short bio.

Once key-wrapping support is ready, a profile server will be set up to save data and provide a sync mechanism across multiple devices. All data stored on the profile server will be client side encrypted much in the same way as Firefox Sync operates today. Keys to unencrypt the stored data will not leave the user's devices, making the data unaccessible to third parties who have access to Persona's servers.

##Data collected
Initially, only a minimal set of data will be requested from the user. The attributes collected are name and photo. In the future, additional attributes will be stored in multiple "contact cards". Additional data likely includes address, phone number, D.O.B., a web site, twitter handle, facebook handle, and possibly a short bio. The exact list of extended attributes which are collected have yet to be determined.

##Data retention
Until key wrapping support is ready, profile data will be retained only on the user's device. When a user manually signs out of Persona or a new user signs in on the device, the original user's profile data will be cleared.
When key wrapping support is complete and client side encryption is possible, a profile server will be set up which acts as a sync mechanism. This data will be retained on Mozilla's servers but will be unaccessible by ourselves or by third parties as the keys to unencrypt the data will not leave the user's devices.

##Comparisons
Facebook Connect and OAuth?

##User Data
Concrete user data that will initially be collected:

{
name: <string>
photo: <base-64 encoded image>
}

##Users affected
All Persona users will be affected by this proposal. Approximately 100,000 sign-ins/month.

##Opt-in/Opt-out
All features will be opt-in. Users will not have to supply profile information. When sites request information, users can decline the request or modify any data before it is sent.

##Privacy Policy
Profile data collection and release may require a privacy policy update. Changes to our privacy policy will be made and published before this service is released.
Profile information that a user releases to a site will be governed by that site's privacy policy and TOS.

##Publication of Collected Data
An individual user's profile data will never be published by Mozilla. We may publish aggregate information relating the number of users using the service or KPI indicators.

Profile information that a user releases to a site will be published at that site's discression.

##Background Bugs & Wiki Pages