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 <[email protected]> wrote: > 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 <[email protected]>: >> 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 required when the request comes from a >> browser but then not have login required when the request comes from >> the app? -- 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 email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CACwCsY4VXrmj7TExnDRVqSmJ5GJU5jn4_%3DBi_hpX4-yABSUfew%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
