All users were logged out of Bugzilla on October 13th, 2018
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 TreeStatus / api.pub.build.mozilla.org/treestatus/ 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. Here is a 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
:dustin In advance of the shutdown of Persona on November 30th, 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 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. : https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers : http://identity.mozilla.com/post/27122712140/new-feature-adding-your-websites-name-and-logo
This specific bug is easy, the current implementation of treestatus (the one in c#0) is using "RelengApi"'s login mechanic, which is based on a hook into our LDAP at present. (and will be migrated to using Taskcluster's auth in the future, as we migrate services in it to heroku). The *old* implementation used persona, and the expectations itself does require non-employee access but all-who-can-access are part of LDAP. /me presses his Staples Easy Button and moves on.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WORKSFORME
In case comment 2 is ambiguous to someone not familiar with TreeStatus/Relengapi: * There was a compete rewrite of TreeStatus last year * The new implementation does not use Persona * The old implementation (previously hosted at treestatus.mozilla.org) has been decommissioned The new TreeStatus site: https://api.pub.build.mozilla.org/treestatus/ And source: https://github.com/mozilla/build-relengapi/tree/master/relengapi/blueprints/treestatus
Great, thanks for the details.
Status: RESOLVED → VERIFIED
Resolution: WORKSFORME → FIXED
You need to log in before you can comment on or make changes to this bug.