At 09:14 AM 5/18/00 -0700, Paul wrote:
>We're upgrading from an NCSA only server to DigiCerts using Apache
>w/modperl & modssl. We have *lots* of scripts in various languages
>expecting the company-specific ID code in REMOTE_USER, so I'm hacking
>it in with Perl*Handlers.
>
>Is there a way (such as with $c->user) to get the *browser* to report
>the right username on subsequent requests without a login dialogue?
No. You need to pass remote user to the browser using a form var then. I
assume you are making use of JavaScript or Java or some other client side
stuff.
Your message is a little confusing to me as to what you are accomplishing
since you open up with a server-side scenario and then close with a
question about client-side behavior being affected by possibly setting
$c->user?
Anyway, if your concern turns out to be server side, writing a handler to
set REMOTE_USER should be fairly simple since mod_ssl is extremely flexible
with the information it exports to the environment from the digital cert.
All you need is an appropriate set of mapping rules.
BTW, just because you use digital certs does not necessarily preclude you
from a basic auth system either for these old scripts. Digital certs are
transferred on the SSL stream, Basic Auth credentials are transferred after
the SSL Stream is authenticated. Although it seems a pain.
Anyway, since I didn't quite understand where your issue comes from, I
included more information than you probably wanted. Sorry about that in
advance.
Good Luck,
Gunther
__________________________________________________
Gunther Birznieks ([EMAIL PROTECTED])
Extropia - The Web Technology Company
http://www.extropia.com/
