1273037 - Replace Persona with an alternative login solution on https://analysis.telemetry.mozilla.org/

Status: RESOLVED FIXED

(Cloud Services Graveyard :: Metrics: Pipeline, defect, P2)

Description

[Ryan Kelly [:rfkelly]]

(Hopefully this is the right component...)


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 the telemetry dashboard 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.

Comment 1

[Ryan Kelly [:rfkelly]]

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

[Gene Wood [:gene]]

:mreid,

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

Comment 3

[Mark Reid [:mreid]]

(In reply to Gene Wood [:gene] from comment #2)
> :mreid,
> 
> 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.
Great! that would be appreciated!

> 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.
Yep, I'm one of the folks who can modify the auth code for atmo. I'm also adding a ni? for :rvitillo and :mdoglio who are in that group. We have been working on an updated version of the codebase at [1], so this is pretty good timing. Roberto and Mauro, please chime in if you have other thoughts on this.

> 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.
In-bug is good.

> * Has an alternative authentication solution been selected for the site, if
> so what is the new planned auth solution?
I would like to move to LDAP (potentially using SSO or Google Accounts).

> * Is there a timetable and resources to complete the development of the
> change before November 30th?
That seems like a reasonable timeline.

> * 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.
If you have specific recommendations, that would be great. We'll be moving to Django, hopefully that's one of the reference frameworks.

> * 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?
Currently it's limited to Persona users with an email ending in "@mozilla.com" or "@mozilla.org". The general public does not log in.

> * 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?
Since we don't currently have access to any metadata, we don't have anything that requires it. It could potentially be useful in the future for enabling per-dataset access control, resource limits, etc.

> * Does your site accept other login methods beyond Persona currently (e.g.
> github, mozillians, google+) and if so which ones?
No

> * 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.
Nope, no special branding needs.

One other general consideration is that it would be nice to use the same approach to authentication that we use on sql.telemetry.m.o

[1] https://github.com/mozilla/telemetry-analysis-service

Comment 4

[Mauro Doglio [:mdoglio]]

I was planning of using django-allauth and its google authentication backend to replace persona. Let me know if you have any suggestion for something better to use.

Comment 5

[Thomas Huelbert]

as per Roberto, for next sprint

Comment 6

[GitHub Autolander Bot]

Attachment: [telemetry-analysis-service] mozilla:allauth > mozilla:master

Comment 7

[Jannis Leidel [:jezdez]]

This is deployed on the ATMO V2 no, which is currently in alpha (https://atmo-staging.herokuapp.com)

Comment 8

[Ryan Kelly [:rfkelly]]

> This is deployed on the ATMO V2 no, which is currently in alpha

Thanks :jezdez!  For completeness, when should we expect this to hit production?  Is there a tracking but I can follow for the deployment?

Comment 9

[Jannis Leidel [:jezdez]]

:rfkelly That'd be bug 1311634, there is no ETA other than the deadline at the end of the month since we've been stalled by the porting effort.