Another option is to do all the authentication in Apache and use the Django
RemoteUser backend. This would require writing an Apache authnz module to
talk to the c++ server, and adjusting your Apache configs to require
valid-user. Or, if not Apache, whatever server you are using.
Nothing about aut
On Tue, Jun 07, 2016 at 01:44:29PM -0700, Daniel Wilcox wrote:
> Two options:
>
> 1. Tie into Django Authentication
>
> You can make a custom authentication backend and do whatever you want for
> authentication -- including talk over a named pipe and get the OK for users
> if you like.
>
> With
Two options:
1. Tie into Django Authentication
You can make a custom authentication backend and do whatever you want for
authentication -- including talk over a named pipe and get the OK for users
if you like.
With that you'll be able to use the login_required decorator. To make a
authenticatio
hey bro thanx,but i am not using django authentication pattern.
so @login required will not work in my condition.
>
>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an emai
Did you use the login_required decorator on your view? Authentication is
something you have to specify you want for a page, it is not assumed.
https://docs.djangoproject.com/en/1.9/topics/auth/default/#the-login-required-decorator
On Thu, Jun 2, 2016 at 3:54 AM, prabhat jha
wrote:
> i have cre
5 matches
Mail list logo
