Protect vs Authenicate
This WebDNA talk-list message is from 1997
It keeps the original formatting.
numero = 10566
interpreted = N
texte = My understanding is that[protect group1] is used for groups as definded in webcatalog security. and [authenicate realm] is used for realms as definded in WebStar.When using [protect group1] and a person enters a page with this at the top, it shows up with a warning, authorization fail, do you want to retry. It would seem to me that if they failed that webcatalog should throw up the name password dialog box first, just like entering a definded realm in webstar not the alert box first. I am testing this feature on a Lan, and have to enter a username passowrd to get into our intranet to start with. Not tested via remote dial-up. The reason I bring this up is that if the username and password is set to enter a realm in webstar first, and my group1 name and passowrd are identical, I cross over into the protected page with no alert or dialog box appearing, which is ok by me. This allows me to protect the admin of data bases inside our intranet realm which is a very nice feature.What I am driving at is looking at trade accounts vs public accounts for online ordering and I would like a more gracefull entry into a [protect group1] page, then the alert box first. Or did I totally miss something.[authenicate realm] has me confused. If I have a realm definded in webstar already. The client needs to enter a username password to get into this realm as controlled by webstar. Why control it again? Or is there an intended use of this command that I am not getting a grasp of? and the [username] [password] online reference docs make reference to these being used by realms and not groups.Really like the [protect group1], allows very easy remote admin of the data base. Hate realms, because I believe they only can be admin'ed by webstar admin, and allowing remote users into webstar admin is not good :)Now if I am 100% off base, don't beat me up to bad.=============================================== Gary Richter PanaVise Products, Inc. 7540 Colbert Dr. Reno, Nevada 89511 Ph: 702.850.2900 Fx: 702.850.2929 Email: grichter@panavise.com http://www.panavise.com =============================================== ------------------------------------ To leave this talk list send an email to macjordomo@smithmicro.com with BODY unsubscribe WebDNA-Talk ------------------------------------
Associated Messages, from the most recent to the oldest:
My understanding is that[protect group1] is used for groups as definded in webcatalog security. and [authenicate realm] is used for realms as definded in WebStar.When using [protect group1] and a person enters a page with this at the top, it shows up with a warning, authorization fail, do you want to retry. It would seem to me that if they failed that webcatalog should throw up the name password dialog box first, just like entering a definded realm in webstar not the alert box first. I am testing this feature on a Lan, and have to enter a username passowrd to get into our intranet to start with. Not tested via remote dial-up. The reason I bring this up is that if the username and password is set to enter a realm in webstar first, and my group1 name and passowrd are identical, I cross over into the protected page with no alert or dialog box appearing, which is ok by me. This allows me to protect the admin of data bases inside our intranet realm which is a very nice feature.What I am driving at is looking at trade accounts vs public accounts for online ordering and I would like a more gracefull entry into a [protect group1] page, then the alert box first. Or did I totally miss something.[authenicate realm] has me confused. If I have a realm definded in webstar already. The client needs to enter a username password to get into this realm as controlled by webstar. Why control it again? Or is there an intended use of this command that I am not getting a grasp of? and the
[username] [password] online reference docs make reference to these being used by realms and not groups.Really like the [protect group1], allows very easy remote admin of the data base. Hate realms, because I believe they only can be admin'ed by webstar admin, and allowing remote users into webstar admin is not good :)Now if I am 100% off base, don't beat me up to bad.=============================================== Gary Richter PanaVise Products, Inc. 7540 Colbert Dr. Reno, Nevada 89511 Ph: 702.850.2900 Fx: 702.850.2929 Email: grichter@panavise.com http://www.panavise.com =============================================== ------------------------------------ To leave this
Talk List send an email to macjordomo@smithmicro.com with BODY unsubscribe WebDNA-Talk ------------------------------------
grichter@panavise.com (Gary Richter)
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:
[WebDNA] Webcat 6 - MacIntel - iTools (2008)
Forumulas.db & Variables (2002)
Price Not Appearing (2000)
NT Manual (1997)
something simple? (1998)
Payment Processors (2005)
Exclamation point (1997)
RequiredFields template (1997)
[carts] and databases (1997)
Separate SSL Server (1997)
requiredfields HELP!! (2001)
[cart] clarification... (1997)
[WebDNA] eCommerce System Release (2018)
ANother SHOWIF problem (1997)
POST Datamissing? (1998)
OT: Alias/Shortcut on Windows server (2003)
Re:Variable Math (1998)
Re:multiple digests, please stop (1997)
Sorting when searching with grouped fields (2002)
RE: protect tag on NT (1997)