> > Also have a look at > http://web2py.com/books/default/chapter/29/09/access-control#Using-web2py-to-authorize-non-web2py-apps > . >
Here's an example of how the above would be achieved with Nginx: https://github.com/shopware/devdocs/blob/master/source/blog/_posts/2015-03-02-sso-with-nginx-auth_request.md. So, in web2py you just need to set up an action to check for login and return either a 200 response or a 401 or 403. Nginx will then check that action on each request and manage the redirect to the web2py login page if the user is not logged in. This is still not the most efficient approach, as every request is still hitting web2py. Using web2py as a CAS provider is probably better, though it will require the other apps to implement an authentication check and redirect to the web2py application for login, etc. Anthony -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.