Re: [web2py] Question about the necessity to have 2 auth_user tables in a web2py app.... ?

2012-09-20 Thread pbreit
I'd just use one app and one auth_user table. And then use groups or some sort of permissioning. Keep it simple. On Friday, September 14, 2012 6:02:30 PM UTC-7, Don_X wrote: Richard ... Villas ... thank you both for your insights ... for now .. I will go on ... and will try to figure it

Re: [web2py] Question about the necessity to have 2 auth_user tables in a web2py app.... ?

2012-09-14 Thread Richard Vézina
Use group! 2 apps means you will have to tell your user on which app to load or hack something to redirect request of login to the other so the user can log seamlessly from a single app, but this may be bring security holes. I really don't see why you can just put your particular users in a

Re: [web2py] Question about the necessity to have 2 auth_user tables in a web2py app.... ?

2012-09-14 Thread Le Don X
Richard ... Villas ... thank you both for your insights ... for now .. I will go on ... and will try to figure it out as I go along ... I will probably end up trying both approach and see / compare etc .. I foresee issues of various bottlenecks in an app like this .. so .. ... lately ..

[web2py] Question about the necessity to have 2 auth_user tables in a web2py app.... ?

2012-09-13 Thread Don_X
Hello folks ... There is a bit of similarity with another thread below regarding 2 auth_user tables ( for 2 different logins or authentification methods in the same app) ! but before I dive in the question I want to ask, I need to share a bit of the nature and the genesis of the project that

Re: [web2py] Question about the necessity to have 2 auth_user tables in a web2py app.... ?

2012-09-13 Thread Richard Vézina
You can't achieve what you want by using group? I mean you have an admin group the one that are in this group can acces your deeper feature strictly reserved... Like that you can always use web2py mechanism to verify if user is a member a given group. To me duplicate auth system is overkill and

Re: [web2py] Question about the necessity to have 2 auth_user tables in a web2py app.... ?

2012-09-13 Thread villas
I definitely agree with Richard. There is no easy way to have two auth systems in one app. From your description, I do not see why you cannot achieve what you wish with one login and giving users the membership of various groups. This is how auth was designed. However, you do have

Re: [web2py] Question about the necessity to have 2 auth_user tables in a web2py app.... ?

2012-09-13 Thread Don_X
Villas ... Two apps ! - that was my previous thought when I started this whole adventure ! .. and I remember I asked questions in regards to 2 apps where one accesses the tables of the other for various purpose .. or simply sharing tables between two web2py apps ! ... I remember I ended up

Re: [web2py] Question about the necessity to have 2 auth_user tables in a web2py app.... ?

2012-09-13 Thread villas
It is trivial for one app to access the data of another. Simply make more than one connection: db = DAL() db2 = DAL(...) db1rows = db(db.auth_user.id 0).select() db2rows = db2(db2.auth_user.id 0).select() But you cannot do joins directly between the tables. You have to work around