Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support "phone" as a provider #511

Closed
jmonster opened this issue May 29, 2017 · 3 comments
Closed

support "phone" as a provider #511

jmonster opened this issue May 29, 2017 · 3 comments
Assignees

Comments

@jmonster
Copy link

One of the Firebase features that got me psyched up was the support for Phone authentication. However, that seems to be absent from emberfire? Ideally it could work just like the existing Torii methods. So, something like...

<button {{action "signIn" "phone"}}>Sign in via your Phone</button>

And whatever else is involved abstracted away to the page that is loaded in the pop-over window.

If this isn't possible or if there is a simple way to extend emberfire to support it that would be very helpful, too.

Mahalo!

@jamesdaniels jamesdaniels self-assigned this Jun 2, 2017
@jamesdaniels
Copy link
Contributor

I'm going to be taking a look at this next week :)

@colinzhang
Copy link

I'd love to hear if anyone has figured this out yet. I took a stab at including the FirebaseUI plugin as a component (based on this gist) but it doesn't open a popup and is giving me a lot of issues related to linking credentials with the torii provider.

Is there a timeline for built-in phone provider support in emberfire?

Appreciate any insight!

@galmi
Copy link

galmi commented Sep 13, 2017

I have made simple provider for phone auth. It can used while it not built-in.
It using prompt window for input confirmation code. If have any ideas how can do it better, it will be great.

https://www.npmjs.com/package/emberfire-phone

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants