Changes

;Service Discovery* Service shares user DB with Firefox Sync* Supports multiple email addresses per account* Email addresses must be verified before they can be used for sign-in* Service implements verified email protocol [todo: link to protocol spec]

* Service is discoverable via a JavaScript;HTML Client-based APIside Implementation* There is a JavaScript Implements verified email protocol JS API that constructs a visible button for users to sign in* Site cannot introspect the JavaScript API or button to discover any user data (including the ID provider), unless the user has opted-into that * Users who have never used the system automatically default to the Mozilla service* Users can disable the discovery mechanism and opt out of everything* Users can opt into a replacement service (assuming another exists)* Adding a replacement service into the discovery flow uses the Open Web Apps infrastructure [tentative]* Adding a service does not require any review or approval by Mozilla* User's choice of Service and provider is persisted server side ;ID Discovery * IDs asserted to sites must be anonymized based on domain* If user opts in, allow ID discovery and verification without prompting the user (without disclosing other information than the ID) ;Account Manager Integration * Service must meet all Account Manager requirements for with a federated ID provider [link to these requirements?] (yes, they don't exist yet)library* On Acct Mgr enabled browsers, users should not see any web-based login pages or disclosure forms, only the sign-in button on the destination site. ;Cross-Browser Support * All major service features must work on other modern browsers without any add-ons or plugins [Supports IE 8+, Chrome, Firefox 4+, Safari ?] ;Verification Flow5* Service JS library must disable itself if the browser natively implements the OpenID 2.0 protocol ;Login FlowAPI* Service accepts Firefox Sync credentials directly (by typing Allows user to sign-in to Mozilla service, using an email & and password) * Service allows users Allows user to register a new Firefox Sync Mozilla account (in content)* Accounts created via a content Implements email disclosure flow should not generate or allude to a sync keyonce signed in* Service allows users to sign-in using a federated ID from another provider iff that federated ID was previously unknown, or was previously associated Communication with a Firefox Sync account and the user allows sign-in using that ID* Signing into an account with an associated federated ID does not allow modifying Firefox Sync account data (e.g., password)* Content login flow should accept Firefox Sync credentials, or attempt email address discovery (webfinger)* If email discovery fails, the content login flow should present a nascar of supported ID providers ;Information Passis done via pop-Through * Service implements OpenID attribute exchange to disclose information we hold ups (e.g., email address)* Provide sites with metadata about the strength and properties of the ID:** First-party sign-in vs federated** Number of associated (verified) federated accounts** User has been been subject to a captcha** Times since last ID verification or captcha* Todo: determine if strength data disclosure requires user consent* Todo: determine if we should pass through data from other services (e.g., user's Twitter usernameprevent clickjacking)  ;SSO requirements* CAS server integration

* List sign-ins to sites with Mozilla ID, sorted by time and manage email addresses (transaction logverified and unverified)* Retain N days of logs (TBD)* Add, remove address* Search list of sites* Re-send verification mail* List connected accounts (identities to which sites where Mozilla ID is an RP)** Add account [Facebook, Twitter, Google, Generic OpenID]** Remove (disconnect) accounthas been used to sign in** Setting to mark Include a connected account as valid timestamp for login into Mozilla IDthe last time a sign-in occurred