-
Notifications
You must be signed in to change notification settings - Fork 663
A few fixes, cleaned up in nice commits #95
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
Conversation
…inSerializer. It makes easier to get the correct signup for custom user models, because application can subclass SocialLoginSeriaLizer and add required fields to the instance.
@philippeluickx Thank you for your great work! Did you get it work with https://github.com/sahat/satellizer?
|
Hey @ClairePhila !
|
Hi @philippeluickx ! Do you no a sample project using both technologies? |
The redirect needs to be set on both the frontend (satellizer) and backend, the same value. Check out the docs in the code at https://github.com/Tivix/django-rest-auth/blob/master/rest_auth/registration/views.py#L98 Make sure your facebook settings are correct too. |
Thank you again, @philippeluickx ! |
The redirect value is just a common agreed value. If I remember correctly, it does not actually do a redirect to that page. My front-end is pretty simple, this should work: /**
* @name authenticate
* @desc authenticate a user with a social provider
* @memberOf application.authentication.controllers.LoginController
*/
function authenticate(provider) {
$auth.authenticate(provider)
.then(function(response) {
$state.transitionTo('home');
})
.catch(function(response) {
});
}; I assume there is a 2-step process:
|
Add drf template auth customization
Based on my own needs and a few issues.