Re: Multiple 'Users.db' files not possible
This WebDNA talk-list message is from 1997
It keeps the original formatting.
numero = 15824
interpreted = N
texte = I've been following this thread and now I'm really confused. Like Brian, my client wants to have their own database of users that will need to supply a user name and password to be entitled to access certain pages on their site. The client needs to be able to add, modify and delete users in this database, and I do not see a way to prevent them from seeing the contents of the entire users.db file if I allow them this type of access. Additionally, their database will need to have a lot more info than just name and group for each of their users. Can the [protect] tag be used with any database, or does it only refer to users.db? Kenneth Grome wrote: > > >Hi Kenneth! > >I think you are missing my point. Specifically, I want my customer to be > >able to add and delete dealers as needed from a database that protects info > >in the web site. I don't want my customer to be able to modify any other > >user accounts outside of their domain, nor do I really want to give them > >access to the admin group. Tha't why I think a subusers.db for a given > >website would be a good solution, don't you? > > No Brian, sorry, but I think the problem here is that you're not > understanding how the Users.db works with [protect] tags. You can > create any number of different groups of users in that db, and you > can decide which specific users get access to which pages ... based > on the groups they belong to. > > There's no reason you should let anyone belong to the ADMIN group > except administrators ... but that dowsn't mean you can't create any > number of sub-administration groups, each with its own access levels > and security preferences. > > And instead of only using [protect admin] in your pages, you *could* > be using tags like [protect admin,subadmin,members,vendors] or > [protect admin,client1] for example. > > In other words, anything you think you need a subusers.db for, you > can do with the users.db. It may not be obvious until you spend more > timethinking about it and using it and learning how powerful the > users.db is, but once you understand it, you'll see what I mean ... :) > > Sincerely, > Ken Grome > ken@iav.com > 808-737-6499 > WebDNA Solutions > http://webdna.net/-- Gil Poulsen, Webmaster************************************************************** * AltiM@c * Phone: (732) 469-2567 * * 429 St. Giles Court * FAX: (732) 469-5823 * * Somerset, NJ * e-mail: help@altimac.com * * 08873 * WWW: http://www.altimac.com * **************************************************************
Associated Messages, from the most recent to the oldest:
I've been following this thread and now I'm really confused. Like Brian, my client wants to have their own database of users that will need to supply a user name and password to be entitled to access certain pages on their site. The client needs to be able to add, modify and delete users in this database, and I do not see a way to prevent them from seeing the contents of the entire users.db file if I allow them this type of access. Additionally, their database will need to have a lot more info than just name and group for each of their users. Can the
[protect] tag be used with any database, or does it only refer to users.db? Kenneth Grome wrote: > > >Hi Kenneth! > >I think you are missing my point. Specifically, I want my customer to be > >able to add and delete dealers as needed from a database that protects info > >in the web site. I don't want my customer to be able to modify any other > >user accounts outside of their domain, nor do I really want to give them > >access to the admin group. Tha't why I think a subusers.db for a given > >website would be a good solution, don't you? > > No Brian, sorry, but I think the problem here is that you're not > understanding how the Users.db works with
[protect] tags. You can > create any number of different groups of users in that db, and you > can decide which specific users get access to which pages ... based > on the groups they belong to. > > There's no reason you should let anyone belong to the ADMIN group > except administrators ... but that dowsn't mean you can't create any > number of sub-administration groups, each with its own access levels > and security preferences. > > And instead of only using [protect admin] in your pages, you *could* > be using tags like [protect admin,subadmin,members,vendors] or > [protect admin,client1] for example. > > In other words, anything you think you need a subusers.db for, you > can do with the users.db. It may not be obvious until you spend more > timethinking about it and using it and learning how powerful the > users.db is, but once you understand it, you'll see what I mean ... :) > > Sincerely, > Ken Grome > ken@iav.com > 808-737-6499 > WebDNA Solutions > http://webdna.net/-- Gil Poulsen, Webmaster************************************************************** * AltiM@c * Phone: (732) 469-2567 * * 429 St. Giles Court * FAX: (732) 469-5823 * * Somerset, NJ * e-mail: help@altimac.com * * 08873 * WWW: http://www.altimac.com * **************************************************************
Gil Poulsen
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Delayed Redirect (2000)
RE: [WebDNA] Installing WebDNA on VPS (2008)
WebCat2b13 Command Reference Doc error (1997)
WebDav (2001)
[SendMail] from a form? (1998)
WebMerchant 1.6 and SHTML (1997)
[WebDNA] An actual attempt to get WebDNA and MAMP Pro to work - (2018)
[writefile] (1997)
wc 2 pro users - sites, quotes wanted (1997)
two unique banners on one page (1997)
[url] (1997)
WebCat2final1 crashes (1997)
Webcat2, WebCommerce, Mod 10 etc. (1997)
[append] and SSL (1997)
webDNA and ASP pages (1997)
Running 2 two WebCatalog.acgi's (1996)
[WebDNA] [TEST] (2009)
Is this possible, WebCat2.0 and checkboxes (1997)
Summarising on two fields (1998)
math with a [numfound] (2005)