Confirm
110
edits
Changes
Updating links and text
When the Mozilla Identity team [https://web.archive.org/web/20170304142228/http://identity.mozilla.com/post/78873831485/transitioning-persona-to-community-ownership transitioned the Persona login system to community ownership], we committed resources to operational and security support throughout 2014, and [https://groups.google.com/forum/#!topic/mozilla.dev.identity/rPIm7GxOeNU renewed that commitment for 2015]. Due to low, declining usage, we are reallocating the project’s dedicated, ongoing resources and will shut down the persona.org services that we run.
Mozilla will end [ended support for the persona.org service on November 30th 2016](https://groups.google.com/g/mozilla.dev.identity/c/mibOQrD6K0c/m/kt0NdMWbEQAJ), and we expect to fully decommission [https://bugzilla.mozilla.org/show_bug.cgi?id=1197381 it before was shutdown at the end of 2016].
This page exists to help website owners migrate their sites away from persona.org. Don’t hesitate to reach out to us on the [https://lists.mozilla.org/listinfo/dev-identity dev-identity mailing list] and in the [irc://irc.mozilla.org/#services-dev #services-dev IRC channel] for additional support.
== FAQs ==
=== What will happen in the meantime? ===
Security issues will be resolved in a timely manner and the services will be kept online, but we do not expect to develop or deploy any new features.
Support will continue to be available on the [https://web.archive.org/web/20170222151358/https://lists.mozilla.org/listinfo/dev-identity dev-identity mailing list] and in the [irc://irc.mozilla.org/#services-dev #services-dev IRC channel].
All websites that rely on Persona will need to migrate to another means of authentication during this time.
=== What about the code? ===
All of Persona's code -- core, bridges, shims, and more -- is open source and remains [https://github.com/mozilla/persona available on githubGitHub]. Though this marks the end of Mozilla's direct involvement in Persona, we encourage others to continue learning from and building upon our work.
== Migration Suggestions and Guidelines ==
We intentionally designed Persona to expose email addresses rather than opaque identifiers, which should ease the transition to other systems that provide verified email addresses.
Mozilla-hosted sites may find additional, staff-login-specific migration options on the [https://manamozilla-hub.mozillaatlassian.orgnet/wiki/displayspaces/Identity/pages/17236022/Persona+migration+guide+for+internal+sites internal mana page].
=== Delegated Authentication Providers ===
Many large email and service providers offer delegated login for third-party applications, including Google, Facebook and GitHub. Indeed, we have found that many sites currently using Persona also offer login via one or more of these services. While these services do not offer equivalently-strong privacy guarantees to Persona, they are a convenient and secure choice for users since they avoid the creation of a site-specific password.
We plan to offer delegated authentication with Firefox Accounts some time in 2016. If you’re interested in adding Firefox Accounts as a login option to your site, please reach out to us on the [https://web.archive.org/web/20221224205637/https://mail.mozilla.org/pipermail/dev-fxacct/ dev-fxacct mailing list].
=== Site-Specific Accounts ===
We encourage affected reliers to document any alternative solutions here and to discuss them on the dev-identity mailing list, so that others can benefit from their experience.
* The [httphttps://portier.github.io / Portier] open source project attempts to replicate much of Persona's user experience, while being easy to self-host, even on the free tier of PaaS providers like Heroku. Similar to Persona, Portier supports identity-bridging to Gmail. It falls back to passwordless-style login links for everyone else.
