Re: authenticating a second user
This WebDNA talk-list message is from 1997
It keeps the original formatting.
numero = 14380
interpreted = N
texte = >I don't know how to match the entered username/password combination to >the users.db. The first time a user comes in, he is detected and gets his >list of results. But when the next user comes in I don't seem to be able >to have the username cached in the browser replacing the other one. I >think it is because I try to authenticate a new user for the same >realm, I mean the new user has the same privileges than the previous >one. Hi Laurent,Here, you can put this WebDNA into any page that's protected by a [protect] tag, and it will solve your problem. You don't have to change anything, you can copy and paste this WebDNA code exactly as it appears here:
[showif [variable]=[username]] [authenticate New User] [/showif]This will create a button entitled Authenticate which, when clicked, will bring up the browser's authenticate dialog box. The person who clicks this button must enter a *different* username and password than the values currently cached in the browser.And of course, these new values must also be in the Users.db in a record with the same Groups authorization as the group named in the [protect] tag.If the current user is not finished working but happens to accidentally click this button, he/she may use the browser's back button to go back a page or two, thus allowing him/her to finish working without entering a different username/password combination. But that's the *only* way to allow the current user to continue using the site after mistakenly clicking this button ... short of relaunching the browser, of course ... :)Sincerely, Ken Grome WebDNA Solutions http://www.smithmicro.com/webdnasolutions/.
Associated Messages, from the most recent to the oldest:
>I don't know how to match the entered username/password combination to >the users.db. The first time a user comes in, he is detected and gets his >list of results. But when the next user comes in I don't seem to be able >to have the username cached in the browser replacing the other one. I >think it is because I try to authenticate a new user for the same >realm, I mean the new user has the same privileges than the previous >one. Hi Laurent,Here, you can put this WebDNA into any page that's protected by a
[protect] tag, and it will solve your problem. You don't have to change anything, you can copy and paste this WebDNA code exactly as it appears here:
[showif [variable]=
[username]] [authenticate New User] [/showif]This will create a button entitled Authenticate which, when clicked, will bring up the browser's authenticate dialog box. The person who clicks this button must enter a *different* username and password than the values currently cached in the browser.And of course, these new values must also be in the Users.db in a record with the same Groups authorization as the group named in the
[protect] tag.If the current user is not finished working but happens to accidentally click this button, he/she may use the browser's back button to go back a page or two, thus allowing him/her to finish working without entering a different username/password combination. But that's the *only* way to allow the current user to continue using the site after mistakenly clicking this button ... short of relaunching the browser, of course ... :)Sincerely, Ken Grome WebDNA Solutions http://www.smithmicro.com/webdnasolutions/.
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:
WebCat2 beta 11 - new prefs ... (1997)
WebCat2 several catalogs? (1997)
Signal Raised Error (Part III) (1997)
Credit Card not accepted (1998)
Search returns all, not 20 (1997)
Databases going to sleep (1998)
WebCat2b12 - New features for 1.6 users ... (1997)
Problems getting parameters passed into email. (1997)
Re:no [search] with NT (1997)
Tax Rates (1998)
WCf2 and nested tags (1997)
Re:2nd WebCatalog2 Feature Request (1996)
Cancel Subscription (1996)
E-Mail Preferences in Admin Folder (1997)
Cookie set browser session. (1998)
Need some assistance. (1999)
Error, 101 a DNS problem ? (1997)
WebCatalog for guestbook ? (1997)
SMSI - MacWorld (2005)
WCS Newbie question (1997)