3 ms·

I'd see it a bit differently, even if in practice you are right, at least the moment Persona added an account system. But also persona had the core idea that yo

by onli 10y ago

I'd see it a bit differently, even if in practice you are right, at least the moment Persona added an account system. But also persona had the core idea that you get authenticated by proving that you control the email address entered, see https://developer.mozilla.org/en-US/Persona/FAQ#How_does_Persona_verify_a_user%27s_association_with_an_address https://developer.mozilla.org/en-US/Persona/FAQ#How_does_Per.... On top of that there was the browserid API. Portier is passwordless login via email, with optional special handling right now only for Gmail, yes.

k__ 10y ago
So how is the workflow? 1. Click "Login with Portier" 2. Enter email 3. Click on link in email 4. Be logged in ?
- kosinus 10y ago
  Pretty much! 1 and 2 are typically a form on the site using Portier (relying party). There's also less emphasis on branding; as a user you will rarely see Portier mentioned.
- onli 10y ago
  Pretty much, yes. However, ideally you would not "Login with Portier", you would simply "Login". There is no need to mention the infrastructure used (and in our current modules, we simply generate a plain Login-Form without any branding). You also do not have to click on the link, you can enter the code which is in the email. Useful when mixing clients. And finally, when using a email provider with special support (currently: Gmail) you don't click on the email and also don't get one. You just login via Google-Sign-In and get then redirected to the site you are trying to login to. I hope we can support more providers (and custom domains soon). Not having to go into the emails is pretty nice. Edit: Also see https://github.com/portier/portier.github.io/blob/master/Design.md https://github.com/portier/portier.github.io/blob/master/Des... for a more technical view on what happens here.
  - wofo 10y ago
    This is awesome! You automatically get sign in with Google and (in the future) other providers!
    - callahad 10y ago
      Exactly! And you can run one instance for all your projects, regardless of language, instead of having to set up Django-All-Auth for one and Ruby OmniAuth for another. Plus, if we can succeed at the federated discovery protocol part, users gain the ability to host their own authentication endpoint that Portier will automatically delegate to.
  - deleted 10y ago
    [deleted]
  - zimbatm 10y ago
    Would be it be possible to support a `.well-known/portier` to support arbitrary SSO?
    - deleted 10y ago
      [deleted]
    - callahad 10y ago
      Yep, though hopefully we'll be able to avoid reinventing wheels and instead re-use something like WebFinger / WebFist and... something... from OpenID Connect. My immediate concern between now and the end of the Persona shutdown is getting the Gmail + fallback loop stable, audited, and easy to deploy. After that it should be trivial to integrate a federated, email-driven discovery protocol. Just haven't had time to give that proper consideration, yet.
- deleted 10y ago
  [deleted]

by onli 10y ago

k__ 10y ago

So how is the workflow? 1. Click "Login with Portier" 2. Enter email 3. Click on link in email 4. Be logged in ?

kosinus 10y ago
Pretty much! 1 and 2 are typically a form on the site using Portier (relying party). There's also less emphasis on branding; as a user you will rarely see Portier mentioned.
onli 10y ago
Pretty much, yes. However, ideally you would not "Login with Portier", you would simply "Login". There is no need to mention the infrastructure used (and in our current modules, we simply generate a plain Login-Form without any branding). You also do not have to click on the link, you can enter the code which is in the email. Useful when mixing clients. And finally, when using a email provider with special support (currently: Gmail) you don't click on the email and also don't get one. You just login via Google-Sign-In and get then redirected to the site you are trying to login to. I hope we can support more providers (and custom domains soon). Not having to go into the emails is pretty nice. Edit: Also see https://github.com/portier/portier.github.io/blob/master/Design.md https://github.com/portier/portier.github.io/blob/master/Des... for a more technical view on what happens here.
- wofo 10y ago
  This is awesome! You automatically get sign in with Google and (in the future) other providers!
  - callahad 10y ago
    Exactly! And you can run one instance for all your projects, regardless of language, instead of having to set up Django-All-Auth for one and Ruby OmniAuth for another. Plus, if we can succeed at the federated discovery protocol part, users gain the ability to host their own authentication endpoint that Portier will automatically delegate to.
- deleted 10y ago
  [deleted]
- zimbatm 10y ago
  Would be it be possible to support a `.well-known/portier` to support arbitrary SSO?
  - deleted 10y ago
    [deleted]
  - callahad 10y ago
    Yep, though hopefully we'll be able to avoid reinventing wheels and instead re-use something like WebFinger / WebFist and... something... from OpenID Connect. My immediate concern between now and the end of the Persona shutdown is getting the Gmail + fallback loop stable, audited, and easy to deploy. After that it should be trivial to integrate a federated, email-driven discovery protocol. Just haven't had time to give that proper consideration, yet.
deleted 10y ago
[deleted]