[WebDNA] Authentication
This WebDNA talk-list message is from 2009
It keeps the original formatting.
numero = 103547
interpreted = N
texte = --Apple-Mail-5--1023050744Content-Transfer-Encoding: 7bitContent-Type: text/plain;charset=us-ascii;format=flowed;delsp=yesThanks, everyone! I'm in digest mode, so I just saw everyone's assistance this morning.Terry's answer worked beautifully! Just like an SSH authentication. I knew there had to be something there like that!Yes, I do recognize that there are some security risks with any URL- based authentication solution, but since the first domain requires authentication before one can even reach the link in question to the second domain, I feel this is a simple solution that has little risk.Thanks again,Patrick>> I have done this in a similar situation, only on the landing server, > they aren't running WebDNA. But it has realm protection all the > same, so I send the user:password thusly:>> [redirect http://DomainBUSer:DomainBPass@DomainB.com/whatever.html]>> This will perform browser authentication, and on that server, since > you're running WebDNA, you can use [username] and [password] to > check for logged in status (as opposed to setting up a cookie scheme).>> Terry>>> Hi, All ->>>> I have a situation that I can't find addressed in the archive.>>>> I have a client with two domains. Domain A has a domain-specific >> username/password database that I use to set cookies for access. >> Domain B is authenticated by the realm (WebDNA group username and >> password). The client would like it if his users could log in at >> Domain A and then have access to Domain B without logging in again; >> just a link that would carry them through to the other domain, >> already authenticated.>>>> Rather than duplicating the user DB and/or writing cookie code for >> Domain B, is there a way to give the people who have already logged >> in to Domain A access to Domain B? For instance, if I set a master >> name and password in the WebDNA group for Domain B, can I give >> users a link from Domain A that sets the username and password in >> the MIME header, or through a TCPConnect script of some kind?>>>> Thanks!>>>> ----->> Patrick Junkroski--Apple-Mail-5--1023050744Content-Transfer-Encoding: quoted-printableContent-Type: text/html;charset=us-ascii
Thanks, =everyone! I'm in digest mode, so I just saw everyone's assistance =this morning.
Terry's answer worked beautifully! Just =like an SSH authentication. I knew there had to be something there =like that!
Yes, I do =recognize that there are some security risks with any URL-based =authentication solution, but since the first domain requires =authentication before one can even reach the link in question to the =second domain, I feel this is a simple solution that has little =risk.
Thanks =again,
Patrick
I have done this in a =similar situation, only on the landing server, they aren't running =WebDNA. But it has realm protection all the same, so I send the =user:password thusly:
[redirect http://=DomainBUSer:DomainBPass@DomainB.com/whatever.html]
This will =perform browser authentication, and on that server, since you're running =WebDNA, you can use [username] and [password] to check for logged in =status (as opposed to setting up a cookie =scheme).
Terry
Hi, All =-
I have a situation that I can't find addressed in the =archive.
I have a client =with two domains. Domain A has a domain-specific username/password =database that I use to set cookies for access. Domain B is authenticated =by the realm (WebDNA group username and password). The client would like =it if his users could log in at Domain A and then have access to Domain =B without logging in again; just a link that would carry them through to =the other domain, already authenticated.
Rather than =duplicating the user DB and/or writing cookie code for Domain B, is =there a way to give the people who have already logged in to Domain A =access to Domain B? For instance, if I set a master name and =password in the WebDNA group for Domain B, can I give users a link from =Domain A that sets the username and password in the MIME header, or =through a TCPConnect script of some kind?
Thanks!
-----
Patrick =Junkroski
=--Apple-Mail-5--1023050744--
Associated Messages, from the most recent to the oldest:
--Apple-Mail-5--1023050744Content-Transfer-Encoding: 7bitContent-Type: text/plain;charset=us-ascii;format=flowed;delsp=yesThanks, everyone! I'm in digest mode, so I just saw everyone's assistance this morning.Terry's answer worked beautifully! Just like an SSH authentication. I knew there had to be something there like that!Yes, I do recognize that there are some security risks with any URL- based authentication solution, but since the first domain requires authentication before one can even reach the link in question to the second domain, I feel this is a simple solution that has little risk.Thanks again,Patrick>> I have done this in a similar situation, only on the landing server, > they aren't running WebDNA. But it has realm protection all the > same, so I send the user:password thusly:>> [redirect http://DomainBUSer:DomainBPass@DomainB.com/whatever.html]>> This will perform browser authentication, and on that server, since > you're running WebDNA, you can use
[username] and
[password] to > check for logged in status (as opposed to setting up a cookie scheme).>> Terry>>> Hi, All ->>>> I have a situation that I can't find addressed in the archive.>>>> I have a client with two domains. Domain A has a domain-specific >> username/password database that I use to set cookies for access. >> Domain B is authenticated by the realm (WebDNA group username and >> password). The client would like it if his users could log in at >> Domain A and then have access to Domain B without logging in again; >> just a link that would carry them through to the other domain, >> already authenticated.>>>> Rather than duplicating the user DB and/or writing cookie code for >> Domain B, is there a way to give the people who have already logged >> in to Domain A access to Domain B? For instance, if I set a master >> name and password in the WebDNA group for Domain B, can I give >> users a link from Domain A that sets the username and password in >> the MIME header, or through a TCPConnect script of some kind?>>>> Thanks!>>>> ----->> Patrick Junkroski--Apple-Mail-5--1023050744Content-Transfer-Encoding: quoted-printableContent-Type: text/html;charset=us-ascii
Thanks, =everyone! I'm in digest mode, so I just saw everyone's assistance =this morning.
Terry's answer worked beautifully! Just =like an SSH authentication. I knew there had to be something there =like that!
Yes, I do =recognize that there are some security risks with any URL-based =authentication solution, but since the first domain requires =authentication before one can even reach the link in question to the =second domain, I feel this is a simple solution that has little =risk.
Thanks =again,
Patrick
I have done this in a =similar situation, only on the landing server, they aren't running =WebDNA. But it has realm protection all the same, so I send the =user:password thusly:
[redirect http://=DomainBUSer:DomainBPass@DomainB.com/whatever.html]
This will =perform browser authentication, and on that server, since you're running =WebDNA, you can use [username] and [password] to check for logged in =status (as opposed to setting up a cookie =scheme).
Terry
Hi, All =-
I have a situation that I can't find addressed in the =archive.
I have a client =with two domains. Domain A has a domain-specific username/password =database that I use to set cookies for access. Domain B is authenticated =by the realm (WebDNA group username and password). The client would like =it if his users could log in at Domain A and then have access to Domain =B without logging in again; just a link that would carry them through to =the other domain, already authenticated.
Rather than =duplicating the user DB and/or writing cookie code for Domain B, is =there a way to give the people who have already logged in to Domain A =access to Domain B? For instance, if I set a master name and =password in the WebDNA group for Domain B, can I give users a link from =Domain A that sets the username and password in the MIME header, or =through a TCPConnect script of some kind?
Thanks!
-----
Patrick =Junkroski
=--Apple-Mail-5--1023050744--
Patrick Junkroski
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:
AOL (1999)
Another calendar... (2002)
Wanted: More Math Functions (or, Can You Solve This?) (1997)
Num Found by category (2000)
Calendar Solutions (1998)
ShipCosts database (1997)
Webmerchant + Hubby (1998)
server2003 issue (OT) (2006)
Getting Emailer to send mail (1997)
Banners (1997)
Register First (2000)
Websited Development (1999)
New public beta available (1997)
WHY SO MANY DUPLICATES? (1999)
[SHOWNEXT] Examples (1997)
WebDNA EMail Preference (2005)
Mondo amounts of Mail [long] (1999)
Help with Repost Data msg from form (1997)
input type=file has no value? (2003)
Location of Browser Info.txt file (1997)