Subject: Re: Authenticating users without dialog box
This WebDNA talk-list message is from 1997
It keeps the original formatting.
numero = 14502
interpreted = N
texte = >>>Is there any way to pass username and password information without having>>>to enter it into the browser's authentication dialog box? I'd like to>>>take the information as entered into a page's form and have that treated>>>the same as if it was entered through the browser's dialog (ie, I want to>>>be able to select users from a pop-up menu).>>>>Sure, just put form variables into your form named username and>>password. These values override any values that might be in the>>browser's authentication dialog cache.>>Don't forget, though ... if you want to use those same values on the>following pages instead of having the browser revert back to its>cached username and password values, you will *also* have to put the>username=[username] and password=[password] parameters into your>forms and URLs so these values can be passed along ... :)So, there's no way for these form-entered variables to stick and be treated *exactly* as if they were entered via the browser's authentication dialog? What about for subsequent pages in the protected realm that aren't accessed by using a form? And I'd rather not have the password visible in the URL...Rob MarquardtDesigner/Resident Wirehead, Toast Designwww.toastdesign.com
Associated Messages, from the most recent to the oldest:
>>>Is there any way to pass username and password information without having>>>to enter it into the browser's authentication dialog box? I'd like to>>>take the information as entered into a page's form and have that treated>>>the same as if it was entered through the browser's dialog (ie, I want to>>>be able to select users from a pop-up menu).>>>>Sure, just put form variables into your form named username and>>password. These values override any values that might be in the>>browser's authentication dialog cache.>>Don't forget, though ... if you want to use those same values on the>following pages instead of having the browser revert back to its>cached username and password values, you will *also* have to put the>username=
[username] and password=
[password] parameters into your>forms and URLs so these values can be passed along ... :)So, there's no way for these form-entered variables to stick and be treated *exactly* as if they were entered via the browser's authentication dialog? What about for subsequent pages in the protected realm that aren't accessed by using a form? And I'd rather not have the password visible in the URL...Rob MarquardtDesigner/Resident Wirehead, Toast Designwww.toastdesign.com
Rob Marquardt
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:
[WebDNA] agree? --> [url] broken inside [redirect], on a (2009)
order problem (2006)
New Plug-in and Type 11 errors (1997)
[WriteFile] problems (1997)
[OT] installing binary app (2006)
Anybody see this before? (2006)
Our Webcat site launched (1997)
Java and WebDNA (2002)
[ShowIf] a either fields are blank (1998)
New Web Site Developers Database (1996)
test (2001)
Snake Bites (1997)
Fwd: Protect Tag and Groups (1998)
Just Testing (1997)
Letters as SKU (1998)
WebDNA Speed Test (2008)
OK, here goes... (1997)
Location of Webcat site in folder hierarchy (1997)
WebCatalog 2.0 & WebDNA docs in HTML ... (1997)
more remote admin questions (1998)