Beyond Passwords: Secure Authentication with Mozilla Persona

There's a little more discussion of that over on Lobsters: link . The TL;DR is that URIs just didn't work for the mass public. You had to supplement the login form with a NASCAR-esque wall of logos, which was awful for different reasons. Thus, Portier, and Persona before it, chose to identify users by email addresses. I talk a little bit about that at 9:05 in my PyCon 2013 talk on Persona: ▶ this video

I've learnt a lot from this thread, I'd not heard of Mozilla Persona before. Could it be The One Ring to rule them all? Charles Stross has his Rule34, I propose Rule 42 is that if something exists there must be a YouTube video of it. This one of a Dan Callahan presentation from a few years back ▶ this video With Rule38 being a blend of the two.

Persona didn't have the notion of a global password -- the ideal flow had you authenticating with your email provider, on their domain, which was often completely transparent in cases where you were already signed in to that provider. Try logging into 123done.org with whatever you want @mockmyid.com to get a sense of what that would ideally look like. My talk from PyCon 2013 goes into a little detail about how the protocol works: ▶ this video

Please use Persona, it's this idea but much more thoroughly thought out and tested. Here is a great video about it: ▶ this video If you have not heard of Persona, or have heard of it but don't see what the big deal is / why it's different to "Login with google", "Login with twitter" etc, then go watch this video. It is a very elegant, decentralised solution to the login problem.

Check out around the 16:00 mark in this video: ▶ this video Notice that provisioning (steps 1 and 2) and logging into a site (steps 3 and 4) are two completely independent processes, with the browser mediating any identifiable identity-provider-to-target-site communication.