Passwordless login support about bell HOT 4 CLOSED

I am composing an answer to your questions but until I can formulate it properly, would you like to elaborate on why you think it would fit in bell's scope? I know that's the question you asked but I would like to hear your opinion on it.

from bell.

Types of passwordless systems that I am aware of

1. Public/Private Key - ie. Client Authentication in SSL or SSH Key based authentication
2. OTP - You generate a token on your phone or trusted device. I know it stands for One Time Password :)
3. Service sends a token typically to your email or through SMS
4. Not very related here but visual or behavioral recognition

I believe you may be talking about number 3 so let's concentrate on that for now.

Thoughts

Bell is a third party login plugin for hapi.

This is from the first sentence of our README and what is important is that we are a login plugin, but also specific to third parties. This is why I believe Bell never implemented a local strategy for your own username/password system like there is in Passport.

Bell has been very focused on OAuth 1 & 2 but proposals like Active Directory login or SAML fit very easily as we're authenticating with a third party service in all these cases. But, with no. 3 it seems like we are not dealing with any third parties except potentially for sending the token across.

Because of what I just described and because I don't see any standards describing how to make it secure I would say that it is not within the scope of Bell.

Now, with that said maybe there is a way to generalize this or come up with an interesting API where Bell could do a little bit of work. Maybe it could be generalized with the act of refresh tokens in OAuth 2. Also interesting is to look at https://passwordless.net/ or other implementations like it (in any language). Maybe there is a way to generalize the concept with no 1.

from bell.

Closing this issue for now. If you have any comments to add please feel free to do so and I will reopen it.

from bell.

This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.

from bell.