We have been using django 1.3.0 for a long time. We are now trying to
migrate to 1.5.4. We have not changed any schema or model information. We
have been using two layers of middleware and backends (notably something
based on SSLAuth Django App to authenticate first by certificate issued
fro
et me know if I correctly understood your issue.
>
> Regards
>
> Leonardo Giordani
> Author of The Digital Cat <http://lgiordani.github.com>
> My profile on About.me <http://about.me/leonardo.giordani> - My GitHub
> page <https://github.com/lgiordani> - My Coderw
; On Wednesday, 18 September 2013 18:51:30 UTC+1, Lauri Carpenter wrote:
>
>> We have been using django 1.3.0 for a long time. We are now trying to
>> migrate to 1.5.4. We have not changed any schema or model information. We
>> have been using two layers of middleware
is being calculated by django, not
set by us; our settings.py file does not include any reference to
AUTH_USER_anything).
But when this happens during the authentication portion of the web
interface, it causes the traceback, from somewhere within the
django.contrib.auth forms for logging in (s
Ok, I have found the problem (through digging through to post more
information about it).
It turns out that in our gui application, the gui-specific settings file
was setting:
INSTALLED_APPS = (
'ncis_gui',
'ncis_sslauth',
'django_auth_ldap',
)
and did not include the apps that
5 matches
Mail list logo