Re: authenticating a second user, the sequel
This WebDNA talk-list message is from 1997
It keeps the original formatting.
numero = 14415
interpreted = N
texte = >>
>>[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.>>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 seethe login page. Remember, the login page must have a[protect] tag init, and the new values the user enters into the Browser'sauthenticate 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] contextin it that performs a search based on the Username or Password valuescached by the browseer, that search will retrieve that user's recordsinstantly ... :)Sincerely, Ken GromeWebDNA Solutionshttp://www.smithmicro.com/webdnasolutions/.
Associated Messages, from the most recent to the oldest:
>>
>>[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.>>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 seethe login page. Remember, the login page must have a
[protect] tag init, and the new values the user enters into the Browser'sauthenticate 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] contextin it that performs a search based on the Username or Password valuescached by the browseer, that search will retrieve that user's recordsinstantly ... :)Sincerely, Ken GromeWebDNA Solutionshttp://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:
SKU's (2000)
No luck with taxes (1997)
customer.db and forms (1999)
RE: is sku a REQUIRED field on NT (1997)
WebCat name recognition (1998)
SiteGuard Use Question (1997)
syntax question, not in online refernce (1997)
Re:no template caching (1997)
Banners (1997)
New site announcement + Showing once on a founditems (1997)
Major bug report on rootbeer (1997)
[WebDNA] El Capitan (2017)
Re:2nd WebCatalog2 Feature Request (1996)
^ in a path (2001)
Out of the woodwork (2007)
range searching (1998)
Quick ShowIf question (1997)
WebCatalog Mac and cgi-bin (WebSTAR 2.0) (1997)
NT Setup (1998)
Trigger Problems (2000)