Closed Bug 1273028 Opened 9 years ago Closed 8 years ago

Remove Persona login on MDN

Categories

(developer.mozilla.org Graveyard :: Sign-in, defect)

Product:
developer.mozilla.org Graveyard
Component:
Sign-in
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: rfkelly, Unassigned)

References

Details

(Keywords: in-triage, productwanted)

Persona will be decommissioned by the end of 2016, and I'm trying to ensure that all the work we need to do between now and then is captured under the following meta-bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1197381 I couldn't find an existing bug for migrating MDN away from Persona, so I'm creating one. If there is an existing bug, please link it under the above meta-bug and close this one out. (I found Bug 1265546, but it didn't seem to capture the work of actually replacing Persona with something else)
Also, I just realized, I should have linked to this page with more information on migrating away from Persona, which we'll continue to maintain and update over the year as various Mozilla properties make the move: https://mana.mozilla.org/wiki/display/Identity/Persona+migration+guide+for+internal+sites
See Also: → 1260257
Severity: normal → major
Keywords: in-triage, productwanted
:groovecoder, :hoosteeno, Hi, I'm part of the Mozilla Enterprise Information Security team (previously called Opsec) and the previous devops engineer for Persona. In advance of the shutdown of Persona on November 30th[1], I was hoping to both find out what was planned, in regards to authentication, as well as offer up assistance and alternatives if needed. Firstly, I'm hoping to communicate with either the developer/development team capable of modifying the authentication code for the site or the manager responsible for the site. If I've made this request to the wrong person, please let me know, and feel free to ignore the questions below. If you happen to know who the right person is and can share that with me even better. If you'd prefer to just have a short discussion over Vidyo instead of writing a response, that's totally fine, either say so and I'll set it up or send a calendar invite to me to chat. * Has an alternative authentication solution been selected for the site, if so what is the new planned auth solution? * Is there a timetable and resources to complete the development of the change before November 30th? * Would you like any help in coming up with an alternate auth solution? We have reference architectures for a handful of frameworks. If so, either schedule a Vidyo call with me or I will schedule one with you. * How would you characterize your site's userbase? Do users that login currently consist only of people with Mozilla LDAP accounts? Do Mozilla contributors/community also currently log into the site? Does the general public log into the site? * Since your currently using Persona for auth I'm assuming that your site doesn't have access to metadata about users stored in LDAP (e.g. first and last name) or access to LDAP group information of users (e.g. what Mozilla team they're in). Would your site benefit from this type of information if it were available in the new auth solution? * Does your site accept other login methods beyond Persona currently (e.g. github, mozillians, google+) and if so which ones? * Do you currently take advantage of the branding capabilities[2] of Persona which allow you to put your site's logo or site name in the Persona login popup? Do you have requirements for your replacement auth solution related to branding? A specific example around branding is the fact that the Firefox Accounts auth solution has "Firefox" branding associated with the login process which may or may not be acceptable to you for your site. [1]: https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers [2]: http://identity.mozilla.com/post/27122712140/new-feature-adding-your-websites-name-and-logo
Flags: needinfo?(lcrouch)
Flags: needinfo?(hoosteeno)
Thanks! Redirecting this request to Kadir Topal, the product owner for MDN.
Flags: needinfo?(lcrouch)
Flags: needinfo?(hoosteeno)
Flags: needinfo?(a.topal)
+ :jwhitlock
Thanks, Justin. Gene, thanks for reaching out and offering your support. We'll discuss our next steps with Persona next week in London, but in the mean time, I'll try to answer some of the questions you've had. (In reply to Gene Wood [:gene] from comment #2) > * Has an alternative authentication solution been selected for the site, if > so what is the new planned auth solution? Currently we offer Github as the alternative solution in parallel to Persona. We haven't decided yet whether we want to offer any other authentication methods. > * Is there a timetable and resources to complete the development of the > change before November 30th? No, not yet > * Would you like any help in coming up with an alternate auth solution? We > have reference architectures for a handful of frameworks. If so, either > schedule a Vidyo call with me or I will schedule one with you. Thanks a lot for the offer, I'm sure we'll take you up on that :) > * How would you characterize your site's userbase? Do users that login > currently consist only of people with Mozilla LDAP accounts? Do Mozilla > contributors/community also currently log into the site? Does the general > public log into the site? We have all three groups using Persona at the moment. Persona accounts are used by 76% of users on MDN. > * Since your currently using Persona for auth I'm assuming that your site > doesn't have access to metadata about users stored in LDAP (e.g. first and > last name) or access to LDAP group information of users (e.g. what Mozilla > team they're in). Would your site benefit from this type of information if > it were available in the new auth solution? Yeah, I'm pretty sure we don't have that information at the moment. It's not particularly important to us either. > * Does your site accept other login methods beyond Persona currently (e.g. > github, mozillians, google+) and if so which ones? Github > * Do you currently take advantage of the branding capabilities[2] of Persona > which allow you to put your site's logo or site name in the Persona login > popup? Do you have requirements for your replacement auth solution related > to branding? A specific example around branding is the fact that the Firefox > Accounts auth solution has "Firefox" branding associated with the login > process which may or may not be acceptable to you for your site. We do make use of Persona's branding capability, but we don't depend on it. The Firefox branding for Firefox Accounts is somewhat unfortunate, but not a deal breaker for us.
Flags: needinfo?(a.topal)
Updating bug title to reflect the chosen solution: * July 2016: Announce Persona going away, discourage for new accounts * Late July 2016: Disallow Persona for new accounts, email users with only Persona * November 1st, 2016: Turn off Persona login for existing users
Summary: Replace Persona with an alternative login solution on MDN → Remove Persona login on MDN
Commits pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/f46efe294d561569a1ae49e77b60033f120a0829 Bug 1273028: Escalating Persona shutdown warning. Now red with a deadline. https://github.com/mozilla/kuma/commit/d2136e692a40822dcd0797810b93541755581597 Merge pull request #4017 from mozilla/1273028-persona-warning-zomg Bug 1273028: Escalating Persona shutdown warning.
Commits pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/db6711a8ae76ca5493b9f47800832b7e3b48737a Bug 1273028: Fix typo in warning message. https://github.com/mozilla/kuma/commit/712f010e1d827bd06b51f982a7309a4e88ceb907 Merge pull request #4018 from mozilla/1273028-persona-warning-zomg Bug 1273028: Fix typo in warning message.
Commits pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/5fb45f9ae67a4e89e0b68a9571c3c6d8b9864f94 bug 1273028: Persona UI changes, related tests https://github.com/mozilla/kuma/commit/0bd7f983e1cacd6e532efd68094715e620bbfb38 bug 1273028: Switch to GitHub only in tests https://github.com/mozilla/kuma/commit/bdb4f366d58742d979ffb82f6982a33626eee8c5 bug 1273028: Add recovery of Persona account https://github.com/mozilla/kuma/commit/afaa14e81b8641b7c879274369b1b103a287b3d4 bug 1273028: Drop account connections page With Persona gone, and no way to add a second GitHub account, the Account Connections page is unneeded. https://github.com/mozilla/kuma/commit/aae7ee511e6ad027e7c2d31ce0b810973a32a88d bug 1273028: Add registration_disabled notice With the login dropdown removed and login choices simplified, there is no good place to put a "profile creation disabled" notebox in the login bar. Instead, put it on the "Please sign in" page, where visitors are mostly likely to see it. https://github.com/mozilla/kuma/commit/17e25c33d6df6c52869b3fa16fc8a437bab6ed9e bug 1273028: Update comments in user workflows Adjust code, test, and comments to explain the new workflows: - Detecting a matching legacy Persona account begins account recovery - We expect GitHub to be the default (only) login - socialaccount_sociallogin was required, may be removed in the near future - There will be more cleanup work after deployment https://github.com/mozilla/kuma/commit/f14d621b571d05c09c56e14f6c1e263a5c7c2196 bug 1273028: Add more matches for recovery emails Send recovery emails: * To users with that primary email (existing method) * To users with a matching Persona account * To users with a matching confirmed email https://github.com/mozilla/kuma/commit/b55320f3d1c664cdcaea3510f175375f6b785928 Merge pull request #4014 from mozilla/1273028-remove-persona bug 1273028 - Remove Persona logins
Persona login has been removed from MDN, and existing Persona users logged out.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Commits pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/aae163af4716bee1ea089fdb1d5e6a82e42b7b75 bug 1273028: Remove Persona provider Remove the Persona provider and application, which was adding a hidden form and JS to MDN pages to enable sign-in. Clean-up other unneeded Persona files and strings. https://github.com/mozilla/kuma/commit/62e3e31ee0c69456dbf6c928eeb6305a8d452f0e bug 1273028: Update install docs for GitHub auth The Account Connections page has been retired, so the process for adding GitHub auth to the manually created admin account has changed. https://github.com/mozilla/kuma/commit/e4c442d46f06ab5eac7dc20fd95ee8bf8ca1b7e5 Merge pull request #4038 from jwhitlock/less_persona_1273028 bug 1273028: Remove Persona provider
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.