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:

    
  1. Re: authenticating a second user, the sequel (Kenneth Grome 1997)
  2. authenticating a second user, the sequel (Laurent Pladys 1997)
  3. Re: authenticating a second user (ltpladys 1997)
  4. Re: authenticating a second user (Kenneth Grome 1997)
  5. Re: authenticating a second user (Christer Olsson 1997)
  6. Re: authenticating a second user (ltpladys 1997)
  7. Re: authenticating a second user (ltpladys 1997)
  8. Re: authenticating a second user (Kenneth Grome 1997)
  9. authenticating a second user (ltpladys 1997)
>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:
[thisurl]> [username]>
[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:

3 card formulas! (1999) japanese characters (1997) I'm having trouble using [url][interpret][math] together in lookup (1997) Typhoon 4 -- yes or no? (2000) A multi-processor savvy WebCatalog? (1997) Forcing Paragraph Breaks on Results (1998) Cart# (1997) WebCat2b13 Mac plugin - [sendmail] and checkboxes (1997) Questions To Answer (1997) StoreBuilder help/question... (2000) WebCommerce Security Alert! (1996) Looking for a host (1997) Question about links (1999) One more time (1997) security (1997) How would I? (2000) Leap Day Triggers? -confirmation- (2000) [WebDNA] Sort by Row (2017) [WebDNA] Build Name for 6.1 (2008) [WebDNA] Is anybody running a CAPTCHA? (2017)