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 thetop, 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 thename password dialog box first, just like entering a definded realm inwebstar not the alert box first. I am testing this feature on a Lan, andhave 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 theusername and password is set to enter a realm in webstar first, and mygroup1 name and passowrd are identical, I cross over into the protectedpage with no alert or dialog box appearing, which is ok by me. This allowsme to protect the admin of data bases inside our intranet realm which is avery nice feature.What I am driving at is looking at trade accounts vs public accounts foronline ordering and I would like a more gracefull entry into a [protectgroup1] page, then the alert box first. Or did I totally miss something.[authenicate realm] has me confused. If I have a realm definded in webstaralready. The client needs to enter a username password to get into thisrealm as controlled by webstar. Why control it again? Or is there anintended use of this command that I am not getting a grasp of? and the[username] [password] online reference docs make reference to these beingused by realms and not groups.Really like the [protect group1], allows very easy remote admin of the database. Hate realms, because I believe they only can be admin'ed by webstaradmin, 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.comwith BODYunsubscribe 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 thetop, 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 thename password dialog box first, just like entering a definded realm inwebstar not the alert box first. I am testing this feature on a Lan, andhave 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 theusername and password is set to enter a realm in webstar first, and mygroup1 name and passowrd are identical, I cross over into the protectedpage with no alert or dialog box appearing, which is ok by me. This allowsme to protect the admin of data bases inside our intranet realm which is avery nice feature.What I am driving at is looking at trade accounts vs public accounts foronline ordering and I would like a more gracefull entry into a [protectgroup1] page, then the alert box first. Or did I totally miss something.[authenicate realm] has me confused. If I have a realm definded in webstaralready. The client needs to enter a username password to get into thisrealm as controlled by webstar. Why control it again? Or is there anintended use of this command that I am not getting a grasp of? and the
[username] [password] online reference docs make reference to these beingused by realms and not groups.Really like the [protect group1], allows very easy remote admin of the database. Hate realms, because I believe they only can be admin'ed by webstaradmin, 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.comwith BODYunsubscribe 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:
WebCat2 beta 11 - new prefs ... (1997)
Secure Server (1997)
Dedicated hosting recommendations (2000)
New (1998)
WebCatalog 4.0.2b5 available (2000)
Unable to view next 101-200 (1997)
About WebDNA (2006)
Almost a there but..bye bye NetCloak (1997)
A quickie question (1997)
[ShowIf] and empty fields (1997)
Huge databases and RAM (1998)
Feature discussion: simple way for [url] and [convertchars] (2000)
RequiredFields template (1997)
Why doesn't it change? (1998)
Summing fields (1997)
Problems with [Applescript] (1997)
Range Comparisons (2000)
[append] problem (1997)
WebCat2b13MacPlugIn - [include] doesn't allow creator (1997)
Help! WebCat2 bug (1997)