Wil — Fri, 22 Feb 2002 10:22:28 +0000

Hi Taff

I'm preety sure one of the following programs will accomodate your needs:

http://cgi.resourceindex.com/Programs_and_Scripts/Perl/Password_Protection/

Let me know if you find something there you like. I'd personally go with the lightweight option, as you don't need the complexity of a database or anything like that.

taff — Wed, 20 Feb 2002 17:51:21 +0000

Yes, currently htpassword but I'm not married to it. I do like to global aspect for myself and my developers though. Not sure how that would be affected by what we're discussing though - I guess I'd have to whip up some sort of developers console...

Maybe this is more trouble than it's worth for the time being. We are talking about ongoing access for less than 6 clients at a time although I'd like to see that grow down the road (wouldn't we all? )

By the way, the page I'm referring to is at:
sitesunseen.com/clients.html

As you'll see, I have links for each individual client (4 at the moment) leading to a htpassword protected folder for each. This is what I thought might look better as a single "client login" box.

Wil — Wed, 20 Feb 2002 13:36:55 +0000

How are they currently authenticated? .htpasswd? Would you mind if this was changed?

taff — Wed, 20 Feb 2002 12:11:36 +0000

Dang, I fell of the page!

Quote: Originally posted by Wil
What you're thinking is a login box on a static page, send the request to the browser then transfer you to the directory based on your login without going through the server-side basic auth of .htaccess etc.?

Wil,

ummm. yeah.. I think

I don't even care if the login box is "in page" or if it is the standard "Enter Network Password" popup, although I would prefer the former. I just want one "Client Login" with multiple destinations based on the user/password

Wil — Fri, 15 Feb 2002 14:14:28 +0000

Hi Taff

Yes, this can be done. What you're thinking is a login box on a static page, send the request to the browser then transfer you to the directory based on your login without going through the server-side basic auth of .htaccess etc.?

Hm, you'd then require a script that could check and pass your htaccess credentials to the webserver before letting you in.

I'm sure this can be done using Perl and a module off CPAN. I'll take a look and get back to you.