Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 247
  • Last Modified:

can't get logon user with proxy

I'm using microchof IIS 2.0 thru an NT proxy. I need to capture the logon user and , inspecting all environ vars at cgi side (REMOTE_USER,AUTH_USER,HTTP_*) , as well as all them listed in MS docs , and the "interesting" ones have the NULL value. If I connect without proxy , everything is OK.
Any suggestions ?
Thanks in advance.
0
aurelio
Asked:
aurelio
  • 2
1 Solution
 
dagmarCommented:
Provided you have installed Perl32 on the NT/95 machine running the webserver, and set up the webserver to be able to execute perl code properly, you can do this very easily...

The perl fragment to do this would (should!) be:

-------8<-------
my $Key;

# You must have this line so the Httpd knows that you are
# delivering an HTML document!
print "Content-type: text/html\n\n";

print "<HTML>\n<HEAD>\n";
print "<TITLE>Environment Variables</TITLE>\n";
print "<BODY>\n";
print "<H1>Environment Variables:</H1>\n";
# This will print out all the environment variables
foreach $Key (keys %ENV) {
  print "$Key = :$ENV{$Key}:<BR>\n";
}
print "</BODY>\n</HTML>";

exit;
-------8<-------
0
 
aurelioAuthor Commented:
Excuse me, but in the the question I say "inspecting all environ vars at cgi side .. " , I mean i've already seen the variable/values. The problem is that , after trespassing the proxy , the "interesting" ones ( logon name ) have NULL.
Thank you for the answer and sorry for the "rejection" .
0
 
dagmarCommented:
If I'm interpreting your English properly, then what you are saying is that you are upset because you are unable to retrieve the identd information about the remote user when they go through a web proxy to reach your server.   (I.e., the username of the user logged in and running the browser on the remote machine.)

Unfortunately for you, this is what's supposed to happen when someone goes through a proxy.  A proxy server usually means they're on the other side of a firewall, and this means that you aren't going to be getting any information about that user anyway, anyhow.  You simply MUST have a clear path from the web server to the client's machine to get identd information back.
Sorry to disappoint you, but such is the nature of firewalls.

...further complicating issues is the fact that most people using graphical browsers are running them under Windows, which does not normally even have identd on it, so ident calls on the remote user will turn up null _anyway_.

0

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now