Closed
Bug 1273036
Opened 10 years ago
Closed 9 years ago
Replace Persona with an alternative login solution on peekaboo.mozilla.org
Categories
(Webtools :: Peekaboo, defect)
Webtools
Peekaboo
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rfkelly, Unassigned)
Details
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 Peekaboo 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.
| Reporter | ||
Comment 1•10 years ago
|
||
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
Comment 2•10 years ago
|
||
:peterbe,
First sorry for the boilerplate-ness of my questions here which you also saw in https://bugzilla.mozilla.org/show_bug.cgi?id=1273027#c2 I'm hoping to ask these questions in distinct tickets to keep the info organized, not to give you unnecessary work. =)
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?(peterbe)
Comment 3•10 years ago
|
||
Peekaboo is deprecated and will soon be replaced.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(peterbe)
Resolution: --- → INVALID
Comment 4•10 years ago
|
||
Peter,
Thanks for the information. Just a few questions.
* When you say replaced do you mean that the app powering Peekaboo is being replaced with a new app? What is it being replaced by?
* Is the site just being decommissioned?
* Do you expect this replacement to take place before Nov 30?
Flags: needinfo?(peterbe)
Updated•10 years ago
|
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Comment 5•10 years ago
|
||
Mark, When will Peekaboo be entirely replaced? Basically, we need to replace it before Persona completely shuts down. That's your deadline :)
Gene, We're entirely moving away from the Peekaboo software. We're switching to a proprietary solution instead.
Flags: needinfo?(peterbe) → needinfo?(mjeffries)
Comment 6•10 years ago
|
||
We plan to move to LobbyConnect by the end of June. We're training WPR on it next week in London.
Flags: needinfo?(mjeffries)
Comment 7•10 years ago
|
||
(In reply to Mark Jeffries from comment #6)
> We plan to move to LobbyConnect by the end of June. We're training WPR on it
> next week in London.
When this happens, could you file a bug in bugzilla.mozilla.org::Administration requesting that the Peekabo component be moved to "Webtools Graveyard"? Thanks :-)
Comment 9•9 years ago
|
||
WPR has moved to LobbyConnect. We are keeping Peekaboo alive until we get a final data export from the database and WPR (the Business Owner) approves the export. Once that's done, we will start the Decommissioning of Peekaboo and I will put in the Peekaboo Webtools Graveyard bug.
Flags: needinfo?(mjeffries)
| Reporter | ||
Comment 10•9 years ago
|
||
The domain no longer resolves, so I assume the decommissioning has completed.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•