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

callback url #3

Open
headwinds opened this issue Dec 12, 2018 · 8 comments
Open

callback url #3

headwinds opened this issue Dec 12, 2018 · 8 comments

Comments

@headwinds
Copy link

headwinds commented Dec 12, 2018

In your awesome post you mentioned that callback url is required but you don't show what you entered in the screenshots nor the post.

Can you share that?

I can run both the frontend and backend apps but it fails on the call back url which is required. Since you say it doesn't matter, I thought to simply put: http://127.0.0.1:4000/

I go through the screen of allowing email in the popup and then this appears:

screen shot 2018-12-12 at 6 44 35 pm

Then I tried http://127.0.0.1:3000/ and I got some nice inception happening

screen shot 2018-12-12 at 5 44 59 pm

I can see the token as a param in that url - but I believe the token should be processed in the backend app not the frontend app. That's why port 4000 should be used....but it's not working.

What did you put as a callback url?

@ivanvs
Copy link
Contributor

ivanvs commented Dec 16, 2018

Hi @headwinds,

I will check this. Thank you for posting this. Currently I am sick, I caught some cold, but when I get better I will look at this.

@headwinds
Copy link
Author

headwinds commented Dec 16, 2018

@ivanvs that would be great - get well first! something may have changed since you created this repo or I may have a bug but seeing your callback url would help rule that out.

If you could run both the frontend and backend on your machine and confirm the twitter login is still working for you that would help too.

I would rather use your approach then resorting to firebase to get social auth

@DanDAAllen
Copy link

Any update on this?

@aravindkumarsvg
Copy link

@CeoFred
Copy link

CeoFred commented Jul 31, 2020

why should that be?? that's not a route on the front end

@abdulqayyum686
Copy link

@ivanvs would you like to resolve this call back issue?
i amd able to redirect to node api after authenrication

@abdulqayyum686
Copy link

Hi please solve out this issue and i think you are fit now

@Muhammad-Faateh
Copy link

Hey. Can you please give an update on this issue?

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

7 participants