|
Taco all you need to do is retrieve the
CGI.AUTH_USER variable (could be CGI.REMOTE_USER I'll have to double check
that), and in a domain environment like Active Directory it will always be
populated with the user's domain user account.....e.g "domain\taco"
I am implementing a similiar system, and all we are
doing is grabbing this cgi variable and comparing it to a security lookup table
which maps these AD user accounts to our own custom security settings. As long
as the user is logged into their machine this CGI.AUTH_USER var will be
populated with their account name.
This should work fine for you in an AD enviroment.
Oh and as far as I have seen this CGI var is left null if you log in to a
standalone pc that isn't part of a doman. So it will only work in a doman
environment,
Hope this helps,
Phil
--- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MX Downunder AsiaPac DevCon - http://mxdu.com/ |
- [cfaussie] Re: Intranet Authentication Via Username Phil Rasmussen
- [cfaussie] Re: Intranet Authentication Via Username Taco Fleur
- [cfaussie] Re: Intranet Authentication Via Username Phil Rasmussen
- [cfaussie] Re: Intranet Authentication Via Username Taco Fleur
- [cfaussie] Re: Intranet Authentication Via Username DoohanOK
- [cfaussie] Re: Intranet Authentication Via Username Scott Barnes
- [cfaussie] Re: Intranet Authentication Via Username Gary Menzel
- [cfaussie] Re: Intranet Authentication Via Username Phil Rasmussen
- [cfaussie] Re: Intranet Authentication Via Username gary menzel
- [cfaussie] Re: Intranet Authentication Via Username Taco Fleur
- [cfaussie] Re: Intranet Authentication Via Username Scott Barnes
