Honestly, I have no idea. All I have is a foggy memory (and lots of
black-box real-world examples out there) from a job that I left 3 years
ago, and I wasn't even particularly involved with the authentication
aspect of the site; it was just there and I want something like it.
So to generalize, I want something where I can continue to count on
Apache to serve up 403s for non-authenticated folks, but not have to
rely on the oh-so-tacky browser-default authentication dialog. Is there
some trick I can pull in PHP to tell the browser "Here's the credentials
the user entered, so supply them and don't go asking the user for them"?
Maybe some header() trickery?
Thanks continually,
~B
Owen Berry wrote:
Are you maybe thinking of Apache::AuthCookieDBI? This is a Perl module.
-- Owen
On Thu, Jul 14, 2005 at 09:06:31AM -0400, Brian Henning wrote:
Hi List,
From a previous employment, I recall an apache module (I think)
called mod_auth_pl, or mod_auth_perl, or some such. I also remember the
website I was working on for that job having a login widget on the page
that took the place of the default browser pop-up authentication dialog,
but still managed (iirc) to interact with the apache authentication
model (i.e. I don't remember there being any fancy footwork other than
.htaccess files to control access, still used Basic auth, but used the
page's widget instead of the browser's pop-up).
I really want to do that for some web pages here. Have a default login
page, instead of having the browser pop up the auth dialog. Am I
remembering poorly, or is that easy to do? I still want my PHP scripts
to be able to use things like $_SERVER["REMOTE_USER"] and such.
Thanks for the advice, folks!
~Brian
--
TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug
TriLUG Organizational FAQ : http://trilug.org/faq/
TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
TriLUG PGP Keyring : http://trilug.org/~chrish/trilug.asc
