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:
Storebuilder Seems to have just died (2003)
WebCatalog NT beta 18 now available (1997)
RE: Can't get appendfile to work (1997)
Ecom Secure? (2001)
Requiring that certain fields be completed (1997)
PIXO support (1997)
WebDNA Writer Needed (1997)
ReturnRaw and redirect (1997)
RE: new cart IDs being assigned somehow (1997)
Lost Serial Number (2004)
[input] [/input] (1997)
Cart Transfer from Un-Secure to Secure (2000)
$Replace with [founditems] (1997)
WebCat2 - Getting to the browser's username/password data (1997)
Listwords and the & (2001)
mem leak: webcat (2001)
E-Mail Formatting (2000)
[OT] Test (2003)
Grant, please help me ... (1997)
Caching pages...again (2001)