Re: selectively requiring login

2016-08-01 Thread Michal Petrucha
On Mon, Aug 01, 2016 at 10:12:53PM +0200, ludovic coues wrote: > The session cookie ? > > Or you could use another decorator or a middle-ware doing > authentication based on the ip and some information passed as get > argument. Like a token returned by django when you auth the user. Using the IP

Re: selectively requiring login

2016-08-01 Thread Larry Martell
How do I get the session cookie from the login and then how do I pass it in the subsequent request? On Monday, August 1, 2016, ludovic coues wrote: > The session cookie ? > > Or you could use another decorator or a middle-ware doing > authentication based on the ip and some information passed as

Re: selectively requiring login

2016-08-01 Thread ludovic coues
The session cookie ? Or you could use another decorator or a middle-ware doing authentication based on the ip and some information passed as get argument. Like a token returned by django when you auth the user. The request hit the new decorator, the decorator notice the user isn't logged in and t

selectively requiring login

2016-08-01 Thread Larry Martell
On Mon, Aug 1, 2016 at 3:03 PM, James Schneider wrote: > > > On Mon, Aug 1, 2016 at 11:33 AM, Michal Petrucha > wrote: >> >> On Mon, Aug 01, 2016 at 12:17:38PM -0400, Larry Martell wrote: >> > I have a view that is accessed both from the browser and from a >> > non-browser app. The request from t

Re: selectively requiring login

2016-08-01 Thread James Schneider
On Mon, Aug 1, 2016 at 11:33 AM, Michal Petrucha < michal.petru...@konk.org> wrote: > On Mon, Aug 01, 2016 at 12:17:38PM -0400, Larry Martell wrote: > > I have a view that is accessed both from the browser and from a > > non-browser app. The request from the non browser app come from a > > rem

Re: selectively requiring login

2016-08-01 Thread Michal Petrucha
On Mon, Aug 01, 2016 at 12:17:38PM -0400, Larry Martell wrote: > I have a view that is accessed both from the browser and from a > non-browser app. The request from the non browser app come from a > remote app where the user has already had to login (or they would > never get to the point where the

Re: selectively requiring login

2016-08-01 Thread Larry Martell
The problem is selectively bypassing or overriding the @login_required decorator. The view is called from an endpoint that has that decorator on it. On Mon, Aug 1, 2016 at 1:52 PM, ludovic coues wrote: > You could use an alternative way to login the user, transparent to the > user. Like giving a

Re: selectively requiring login

2016-08-01 Thread ludovic coues
You could use an alternative way to login the user, transparent to the user. Like giving a token to the app when it login. 2016-08-01 18:17 GMT+02:00 Larry Martell : > I have a view that is accessed both from the browser and from a > non-browser app. The request from the non browser app come from

selectively requiring login

2016-08-01 Thread Larry Martell
I have a view that is accessed both from the browser and from a non-browser app. The request from the non browser app come from a remote app where the user has already had to login (or they would never get to the point where they could cause the request to be sent). Is there a way to make login req