I would suggest saving the username in a cookie.
If the cookie does not exist, pop-up a form, asking for the user name (One time only), then save it in a cookie, hopefully with a fairly long expiration time.
You should also provide a "logout" option, to allow the user to delete the cookie, so you can do tests and impersonation.
Since you are specifically not asking for authentication, this method is specifically NOT secure, but hopefully meets your requirements.
"As you get older three things happen. The first is your memory goes, and I can't remember the other two... "
- Sir Norman Wisdom
| [reply] |
If you're reasonably sure you've got the IP address of the client, you could try working with the samba command "nmblookup" from the Unix side. nmblookup is the samba equivalent of Windows' nbtstat program.
| [reply] |
If your Apache ran on Windows, you'd be able to get the info from $ENV{REMOTE_USER} with the following configuration bits:
LoadModule sspi_auth_module modules/mod_auth_sspi.so
<Location /here>
AuthName "Some realm"
AuthType SSPI
SSPIAuth On
SSPIAuthoritative On
require valid-user
</LOCATION>
Unfortunately, I have no idea if that would ever work on a Unix server (and I doubt it), but I thought I'd throw it out here anyway. It might just give you a lead to google on.
| [reply] [d/l] [select] |