Confirmed users
121
edits
Identity/Persona Shutdown Guidelines for Reliers: Difference between revisions
Identity/Persona Shutdown Guidelines for Reliers (view source)
Revision as of 15:55, 4 July 2024
, 4 July 2024Fix my mistaken use of markdown instead of mediawiki
(Add initial information about persona.org shutdown) |
m (Fix my mistaken use of markdown instead of mediawiki) |
||
| (7 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
When the Mozilla Identity team [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. | 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 [https://groups.google.com/g/mozilla.dev.identity/c/mibOQrD6K0c/m/kt0NdMWbEQAJ ended support for the persona.org service on November 30th 2016], and [https://bugzilla.mozilla.org/show_bug.cgi?id=1197381 it was shutdown at the end of 2016]. | |||
This page exists to help website owners migrate their sites away from persona.org | This page exists to help website owners migrate their sites away from persona.org. | ||
== FAQs == | == FAQs == | ||
=== A website I use requires Persona for login, what should I do? === | |||
You will need to contact the site owner and ask about their plans for migrating away from Persona. | |||
Mozilla staff can find more information about the progress of migrating internal sites | |||
on [https://mana.mozilla.org/wiki/display/Identity/Persona+migration+guide+for+internal+sites this mana page]. | |||
=== Why is persona.org being shut down? === | === Why is persona.org being shut down? === | ||
| Line 15: | Line 22: | ||
=== What will happen in the meantime? === | === What will happen in the meantime? === | ||
Up until November 30th, 2016, Mozilla will continue to support the Persona service at a maintenance level: | |||
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. | 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://lists.mozilla.org/listinfo/dev-identity dev-identity mailing list] and in the | 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 #services-dev IRC channel. | ||
All websites that rely on Persona will need to migrate to another means of authentication during this time. | All websites that rely on Persona will need to migrate to another means of authentication during this time. | ||
| Line 31: | Line 38: | ||
=== What about the code? === | === 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 | All of Persona's code -- core, bridges, shims, and more -- is open source and remains [https://github.com/mozilla/persona available on GitHub]. 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 == | == Migration Suggestions and Guidelines == | ||
| Line 37: | Line 44: | ||
The following alternative login options are available for sites migrating away from Persona. We will continue to update this page throughout the year. | The following alternative login options are available for sites migrating away from Persona. We will continue to update this page throughout the year. | ||
Mozilla-hosted sites may find additional, staff-login-specific migration options on the [https:// | 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://mozilla-hub.atlassian.net/wiki/spaces/Identity/pages/17236022/Persona+migration+guide+for+internal+sites internal mana page]. | |||
=== Delegated Authentication Providers === | === Delegated Authentication Providers === | ||
| Line 43: | Line 52: | ||
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. | 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://mail.mozilla.org/pipermail/dev-fxacct/ dev-fxacct mailing list]. | 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 === | === Site-Specific Accounts === | ||
| Line 64: | Line 73: | ||
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. | 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 [https://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. | |||