Re: 'request' object is always None in auth backend's authenticate()?

2017-02-07 Thread Zoltan Gyarmati
Dear Tim & All, i sent a pull request against master [1], but it would need backporting for the 'stable/1.11.x' branch (it doesn't apply cleanly). Should i send an other PR against 'stable/1.11.x' branch, or it's up to the maintainer to backport it? [https://github.com/django/django/pull/8029]

Re: 'request' object is always None in auth backend's authenticate()?

2017-02-06 Thread Zoltan Gyarmati
Dear Tim & All, thanks for the hint, it works! I filed a ticket [1] and i'm also preparing a PR. Should i send the PR against 'master' or the 'stable/1.11.x' branch? [1] https://code.djangoproject.com/ticket/27815#ticket Thanks, regards Zoltan Gyarmati https://zgyarmati.de On 02/06/2017

'request' object is always None in auth backend's authenticate()?

2017-02-06 Thread Zoltan Gyarmati
Dear All, i'm developing a multi-tenant application where it would be extremely handy to have the request object in my custom authentication backend available, so i went ahead and started to use the /1.11a,/ version, which already has the commit: 4b9330c Fixed #25187 -- Made request available in