Session ID Returns None After Setting Session Data in Django with React Frontend

I'm working on a Django backend with a React frontend and using sessions to manage user authentication. After successfully logging in a user, I'm setting session data (e.g., user_id, name, email, etc.), but the session ID is returning as None despite the session data being correctly stored.

I've configured SESSION_ENGINE to use the database and set SESSION_SAVE_EVERY_REQUEST = True. CORS headers are properly configured with CORS_ALLOW_CREDENTIALS = True. Despite these settings, the session ID isn't being generated or returned correctly, which is causing issues with session management on the client side. How can I resolve this issue and ensure the session ID is properly generated and accessible after login?(https://i.sstatic.net/EawnCfZP.png)

I configured Django's session settings to use database-backed sessions, set SESSION_SAVE_EVERY_REQUEST = True, and enabled CORS with credentials. I expected the session ID to be generated and returned after a user logs in, allowing for proper session management. However, the session ID is returning as None, even though the session data is correctly stored and accessible. I’ve also verified that CORS and session settings are properly configured but still face the issue.enter image description here

It sounds like you've already configured many of the necessary settings for session management in Django. Here are a few additional steps and checks you can perform to troubleshoot and resolve the issue:

1. Ensure Middleware is Correctly Configured

Make sure that SessionMiddleware and AuthenticationMiddleware are included in your MIDDLEWARE settings in settings.py:

MIDDLEWARE = [
    'django.middleware.security.SecurityMiddleware',
    'django.contrib.sessions.middleware.SessionMiddleware',
    'django.middleware.common.CommonMiddleware',
    'django.middleware.csrf.CsrfViewMiddleware',
    'django.contrib.auth.middleware.AuthenticationMiddleware',
    'django.contrib.messages.middleware.MessageMiddleware',
    'django.middleware.clickjacking.XFrameOptionsMiddleware',
]

2. Verify Session Settings

Double-check your session settings in settings.py:

SESSION_ENGINE = 'django.contrib.sessions.backends.db'
SESSION_SAVE_EVERY_REQUEST = True
SESSION_COOKIE_SECURE = False  # Set to True if using HTTPS
CORS_ALLOW_CREDENTIALS = True

3. Check CSRF Settings

Ensure that CSRF settings are properly configured to allow credentials:

CSRF_COOKIE_SECURE = False  # Set to True if using HTTPS
CSRF_COOKIE_HTTPONLY = True
CSRF_TRUSTED_ORIGINS = ['http://localhost:3000']  # Add your frontend domain

4. Use request.session.save()

After setting the session data, explicitly save the session:

def login_view(request):
    # Your login logic
    request.session['user_id'] = user.id
    request.session['name'] = user.name
    request.session['email'] = user.email
    request.session.save()  # Explicitly save the session
    return JsonResponse({'message': 'Login successful'})

5. Debugging Session ID

To debug, you can print the session ID after saving the session:

def login_view(request):
    # Your login logic
    request.session['user_id'] = user.id
    request.session['name'] = user.name
    request.session['email'] = user.email
    request.session.save()  # Explicitly save the session
    print(f"Session ID after login: {request.session.session_key}")
    return JsonResponse({'message': 'Login successful'})

6. Ensure Cookies are Set Correctly

Make sure that the session cookie is being set correctly in the browser. You can check this in the browser's developer tools under the "Application" or "Storage" tab.

7. Cross-Origin Resource Sharing (CORS)

Ensure that your CORS settings allow credentials and the correct origins:

CORS_ALLOW_CREDENTIALS = True
CORS_ALLOWED_ORIGINS = [
    'http://localhost:3000',  # Add your frontend domain
]

8. Check for Proxy Issues

If you're using a proxy (e.g., Nginx), ensure that it is configured to pass cookies correctly.

9. Database Migrations

Ensure that the session table is created in your database by running migrations:

python manage.py migrate

10. Session Expiry

Check if the session is expiring immediately due to some settings:

SESSION_EXPIRE_AT_BROWSER_CLOSE = False
SESSION_COOKIE_AGE = 1209600  # Two weeks
  • Explicitly call request.session.save() after setting the session data:

def login_view(request): # Your login logic request.session['user_id'] = user.id request.session['name'] = user.name request.session['email'] = user.email request.session.save() # Here is where you can Explicitly save the session print(f"Session ID after login: {request.session.session_key}") return JsonResponse({'message': 'Login successful'})

  • set the session for two weeks in your settings.py as you said.

SESSION_EXPIRE_AT_BROWSER_CLOSE = False SESSION_COOKIE_AGE = 1209600

  • or add a Custom Middleware to debug session data on every request::

class SessionDebugMiddleware: def init(self, get_response): self.get_response = get_response

def __call__(self, request):
    response = self.get_response(request)
    print(f"Session ID: {request.session.session_key}")
    print(f"Session data: {request.session.items()}")
    return response
Back to Top