Sounds to me like the authorization system in web2py would work perfectly. Give a set of users access to a subset of the functionality.
Have you read through http://web2py.com/books/default/chapter/29/09/access-control? Using auth_group, auth_membership and auth_permission along with the method decorators should give you all the control you need to restrict these users to a subset of your application. I don't think you need a separate user table, just assign the users to groups. You wouldn't even need permissions, just authorize/restrict based on group membership. Give that a try and then let us know if it will work for you. -Jim On Wednesday, February 14, 2018 at 4:16:50 PM UTC-6, icodk wrote: > > I have a "standard" web2py application that uses the built in > authentication system with sign in, login/out , forgot/change password etc. > In addition, I need to manage "departmental" users that should not have > access to the main application but only to a subset of services. > Is there a way to leverage the authentication system but to use a > different user table. In other words I would like to run two parallel but > separated authentication system > Any idea how to do it ? > -- 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.