Re: Multiple 'Users.db' files not possible
This WebDNA talk-list message is from 1997
It keeps the original formatting.
numero = 15823
interpreted = N
texte = >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/
Associated Messages, from the most recent to the oldest:
>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/
Kenneth Grome
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:
shipcost (1997)
[WebDNA] Does anyone host webdna sites? (2016)
WebCatalog vs. Cold Fusion (1998)
Running _every_ page through WebCat ? (1997)
OT - help.. (2003)
Problems getting parameters passed into email. (1997)
off topic - dna snipets (1997)
[isfile] ? (1997)
WebCat2: Found Items syntax, etc. (1997)
OT: visudo help (2003)
Search/sort in URL Was: GuestBook example (1997)
test (2002)
Spreadsheet App pref. [OT] (2001)
searchable list archive (1997)
Tab Charactor (1997)
Tracking System? (1997)
For those of you not on the WebCatalog Beta... (1997)
Shipping Calculation Problem (1997)
[WebDNA] Search on a database (2012)
RE: Web*SSL and WebCatalog (1997)