title: Using Django Admin History with a custom Login_backend and user model
body: <p>I have a django application using a custom (ldap) login backend and my own extended user model that is used by other applications.</p>
  
  <p>I'm using the django admin extensively but I've only just noticed that the history link leads to a yellow page. I realised that this was due to the fact that I was not using django.contrib.auth and so the auth_user table did not exist.
  I uncommented that in my settings.py and the yellow screen is gone.</p>
  
  <p>The history functionality is not working though and I'm guessing that's because the changes are stored against request.user but the lookup is searching for the user in auth_user.</p>
  
  <p>Does anyone know how to make django admin use my user model table?</p>
  
  <p>If not, does anyone have any idea how I could remove the history link from the admin object view?</p>
  
  <p>Note: I'm looking for the solution with the least editing of the django source code as I will have to justify every line to my superiors.</p>
  
  <p>Any help/suggestions/criticism would be very welcome</p>
  
  <p>Thanks,</p>
  
  <p>Hayden</p>