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:

WebCommerce: Folder organization ? (1997) Nested Loops and SHOWIFs (1997) [WebDNA] A note about the WebDNA Server 8.0.2 installer and Admin (2015) Next (1997) RE: Fishing: anyone on this group willing to do support? (1998) Storebuilder-AutoCategory (2003) shipcost (1997) [format xs] freeze (1997) can WC render sites out? (1997) [dos] command and [math] (1998) Showing once on a founditems (1997) errors.db question (2002) [WriteFile] problems (1997) [WebDNA] [announce] WebDNA Site and Store (2008) Math Function (1997) FOUND: WebCatalog Review by Mike Heck (2001) Max Record length restated as maybe bug (1997) RE: How to verify email address (1997) Ok here is a question? (1997) Some Questions (1997)