基于Django REST Framework+JWT+Angular5的SPA社交登录集成求助

Hey there! I’ve worked with django-rest-social-auth alongside DRF, JWT, and SPAs before, so let’s walk through this step by step to get your social login endpoints working.

Most unresponsive endpoints start with missing or misconfigured settings—let’s verify these first:

• Installed Apps: Make sure rest_social_auth and social_django (the underlying dependency for Python Social Auth) are added to your INSTALLED_APPS in settings.py:

  INSTALLED_APPS = [
      # ... your other apps
      'rest_social_auth',
      'social_django',
  ]
  

• Authentication Backends: Add the necessary backends for your social providers and JWT. For example, if you’re using Google OAuth2:

  AUTHENTICATION_BACKENDS = (
      'social_core.backends.google.GoogleOAuth2',  # Match your chosen provider
      'django.contrib.auth.backends.ModelBackend',
  )
  

• JWT Integration: Ensure your DRF and JWT settings are hooked up to the package’s handler:

  REST_FRAMEWORK = {
      'DEFAULT_AUTHENTICATION_CLASSES': (
          'rest_framework_jwt.authentication.JSONWebTokenAuthentication',
          # Keep your other auth classes if needed
      ),
  }
  
  JWT_AUTH = {
      'JWT_RESPONSE_PAYLOAD_HANDLER': 'rest_social_auth.jwt.jwt_response_payload_handler',
  }
  

• Provider Credentials: Don’t forget to add your social provider’s keys (e.g., Google Client ID/Secret) to settings.py:

  SOCIAL_AUTH_GOOGLE_OAUTH2_KEY = 'your-client-id-here'
  SOCIAL_AUTH_GOOGLE_OAUTH2_SECRET = 'your-client-secret-here'
  

It’s easy to mix up the package’s URL modules—since you want JWT responses, you need to include the urls_jwt module, not the standard urls:

from django.urls import path, include

urlpatterns = [
    # ... your existing routes
    path('social/auth/', include('rest_social_auth.urls_jwt')),
]

This will expose endpoints like /social/auth/google/ (for Google) that return JWT tokens instead of session auth or OAuth2 tokens.

Before blaming the frontend, test the endpoint with a tool like Postman or curl to isolate the issue:

1. Send a POST request to the provider-specific endpoint (e.g., /social/auth/google/)
2. Include these required fields in the request body (JSON format):

   {
       "code": "authorization-code-from-frontend",
       "redirect_uri": "your-registered-callback-uri"
   }
   

If you get no response here, check your Django server logs immediately—there’s likely an error being thrown (e.g., invalid credentials, missing redirect URI match) that’s not being sent to the client.

If the endpoint is silent, enable debug logging for Django and Python Social Auth to see what’s going on:
Add this to your settings.py:

LOGGING = {
    'version': 1,
    'disable_existing_loggers': False,
    'handlers': {
        'console': {
            'class': 'logging.StreamHandler',
        },
    },
    'loggers': {
        'social': {
            'handlers': ['console'],
            'level': 'DEBUG',
        },
        'django': {
            'handlers': ['console'],
            'level': 'DEBUG',
        },
    },
}

Run your server again and send the request—you’ll see exactly where the process is failing (e.g., a missing dependency, a misconfigured provider setting).

If the default JWT payload doesn’t fit your SPA’s needs, you can override the response handler. Create a function in, say, your_app/utils.py:

def custom_jwt_response(token, user=None, request=None):
    return {
        'token': token,
        'user': {
            'id': user.id,
            'username': user.username,
            'email': user.email
        }
    }

Then update your JWT_AUTH setting to use this handler:

JWT_AUTH = {
    'JWT_RESPONSE_PAYLOAD_HANDLER': 'your_app.utils.custom_jwt_response',
}

Give these steps a shot—chances are one of these configuration pieces is missing or incorrect. Let me know if you hit a specific error message, and we can dig deeper!

内容的提问来源于stack exchange，提问作者moh