-
Notifications
You must be signed in to change notification settings - Fork 209
Oauth service not working on current deployment #472
Comments
I am working on this issue |
Hello @isabelcosta , I would like to work on this issue , could you please assign it to me |
Hii @isabelcosta , I would love to work on this issue. Can i proceed ? |
@Aayush-05 I think the URL has to be added to the Google developers console. How do you propose to resolve this? @abhi20161997 who has access to that currently? |
@sammy1997 I am not sure but looks like this hasn't been developed on the backend yet. I couldn't find any authentication backends for these services in the settings file. |
@Aayush-05 @sammy1997 Actually the credentials like CLIENT ID, SECRET KEY, KEY are not provided in the backend(Admin: Social Accounts › Social applications) for the social app provider. After adding these credentials it is working, I have checked for Facebook it is working on my localhost. |
Ah, then maybe they aren't exposed for the development environment. But maybe we can have a dummy set added to the settings file, so any newcomer knows where to add them up. (maybe a section in readme help) |
I want to take up the issue. |
@sakshi1499 I guess you must close this issue |
@ritwickraj78 Great! Thank You! |
Description
Login/Signup via third party apps including Google, Twitter, GitHub, Facebook isn't working on the current deployment and returns the given error.
Mocks
Acceptance Criteria
Update [Required]
Definition of Done
Estimation
5 hours
The text was updated successfully, but these errors were encountered: