Wait, I forgot something! (was Re: authenticating a seconduser, the sequel)

This WebDNA talk-list message is from

1997


It keeps the original formatting.
numero = 14420
interpreted = N
texte = Hey Laurent and anyone else who was ready to do what I just suggested in my previous message ... there's a little more to it than my previous instructions.Not only must you change the [thisurl] tag to the destination page you want your users to login on, but you must ALSO remove the [showif] stuff from the form page and move it to the destination page.In other words, put this on the form page:
Then put this on the destinationPage.dna:[showif [variable]=[username]] [authenticate New User] [/showif] I haven't tested it, but unless I've forgotten something else, I think this should work ... :)>>>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. >> >>Hi Ken, >> >>This worked fine, but what if I want to send my user to a page where he >>gets information extracted from a database based on what he entered in >>the authentication dialog. With this script I have to add a link below >>your authentication code so that AFTER having registered he goes to his >>own page following a link. >>Is there a way to send the user to a new protected page after the >>authentication is cleared ? > > >Yes! > >Instead of using the code exactly as I wrote it above, simply change >[thisurl] to the path to the page you want your user to login on. >Then when he/she enter a new and different (and correct) Username & >Password in the browser's dialog box, the user will immediately see >the login page. Remember, the login page must have a[protect] tag in >it, and the new values the user enters into the Browser's >authenticate box will have to be valid for the group named in the >[protect] tag. > >What's even better is that if your login page has a [search] context >in it that performs a search based on the Username or Password values >cached by the browseer, that search will retrieve that user's records >instantly ... :) > >Sincerely, Ken Grome >WebDNA Solutions >http://www.smithmicro.com/webdnasolutions/ > >. Sincerely, Ken Grome WebDNA Solutions http://www.smithmicro.com/webdnasolutions/. Associated Messages, from the most recent to the oldest:

    
Hey Laurent and anyone else who was ready to do what I just suggested in my previous message ... there's a little more to it than my previous instructions.Not only must you change the [thisurl] tag to the destination page you want your users to login on, but you must ALSO remove the [showif] stuff from the form page and move it to the destination page.In other words, put this on the form page:
[username]>
Then put this on the destinationPage.dna:[showif [variable]=[username]] [authenticate New User] [/showif] I haven't tested it, but unless I've forgotten something else, I think this should work ... :)>>>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. >> >>Hi Ken, >> >>This worked fine, but what if I want to send my user to a page where he >>gets information extracted from a database based on what he entered in >>the authentication dialog. With this script I have to add a link below >>your authentication code so that AFTER having registered he goes to his >>own page following a link. >>Is there a way to send the user to a new protected page after the >>authentication is cleared ? > > >Yes! > >Instead of using the code exactly as I wrote it above, simply change >[thisurl] to the path to the page you want your user to login on. >Then when he/she enter a new and different (and correct) Username & >Password in the browser's dialog box, the user will immediately see >the login page. Remember, the login page must have a[protect] tag in >it, and the new values the user enters into the Browser's >authenticate box will have to be valid for the group named in the >[protect] tag. > >What's even better is that if your login page has a [search] context >in it that performs a search based on the Username or Password values >cached by the browseer, that search will retrieve that user's records >instantly ... :) > >Sincerely, Ken Grome >WebDNA Solutions >http://www.smithmicro.com/webdnasolutions/ > >. 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:

Nutscrape Doesn't Render Right (2002) WC2.0 Memory Requirements (1997) process SSI (1998) several .hdr files with one db file? (1999) UPS QuickCost and More (2000) Shopping Cart Problem (1998) emailer (1997) multiple search commands (1997) WebCat2.0 [format thousands .0f] no go (1997) RE: [WebDNA] WebDNA Roll Call (2013) Web Site (2000) [WebDNA] Not even sure what to ask for help on. . . :( (2008) Database Connectivity (1999) [WebDNA] Small Parsing Problem (2009) Using Applescript to process WebCatalog functions (1998) Development terminated. (1998) Price Not Appearing (2000) Solution help needed (1998) Major Security Hole (1998) MySQL 5/Float (2007)