# Asyncifying django.contrib.auth? (and signals, and maybe sessions)

**URL:** <https://forum.djangoproject.com/t/asyncifying-django-contrib-auth-and-signals-and-maybe-sessions/18770>\
**Category:** Async\
**Created:** [February 10, 2023, 11:09pm UTC](https://forum.djangoproject.com/t/asyncifying-django-contrib-auth-and-signals-and-maybe-sessions/18770 "2023-02-10T23:09:49Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![bigfootjon](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/bigfootjon/32/12068_2.png) [@bigfootjon](https://forum.djangoproject.com/u/bigfootjon)\
**Post date:** [March 8, 2023, 5:23am UTC](https://forum.djangoproject.com/t/asyncifying-django-contrib-auth-and-signals-and-maybe-sessions/18770/5 "2023-03-08T05:23:00Z")

</div>

Both of the above PRs that I mentioned have been merged.

I’ve gone ahead and filed a new ticket ([#34391 (Add async interface to contrib.auth) – Django](https://code.djangoproject.com/ticket/34391)) to track work on an async auth interface, and put a PR ([Fixes #34391: Add async interface to auth by bigfootjon · Pull Request #16636 · django/django · GitHub](https://github.com/django/django/pull/16636)) up for review with the implementation.

That means that in my above proposal:  
#1: In progress, PR is waiting for review  
#2: Done  
#3: Pending creation of a ticket, I’d like to understand the scope of work before I file that  
#4: Blocked on #3, and might need more research into reducing code duplication before starting  
#5: Done  
#6: Partially done during #5, just needs some tweaks to `RemoteUserBackend` after #1 is done

#1 and #3 can be worked on right now, I’m focused on #1 for now. #3 is available if anyone stumbles on to this thread and is interested in contributing!

---

_[View the full topic](https://forum.djangoproject.com/t/asyncifying-django-contrib-auth-and-signals-and-maybe-sessions/18770)._