From: Dancer <dancer@zeor.simegen.com>

It turns out that if you are using an external authenticator, the
username is only logged on _subsequent_ (that is, cached) authentication
hits. If the user's authentication credentials expire from the cache,
their next (initially authenticated) request doesn't log any user info.

I'm pretty sure that this behaviour is unintentional.
Here's a patch:

diff --git a/src/acl.cc b/src/acl.cc
index d273e81ca0377d6f7fa595e7de71f8cb7bcb7560..b14ece1cecc3aaf2505bc30740301b7a3b34b38e 100644 (file)
--- a/src/acl.cc
+++ b/src/acl.cc
@@ -1,6 +1,6 @@
 
 /*
- * $Id: acl.cc,v 1.193 1999/01/12 23:38:35 wessels Exp $
+ * $Id: acl.cc,v 1.194 1999/01/13 22:13:38 wessels Exp $
  *
  * DEBUG: section 28    Access Control
  * AUTHOR: Duane Wessels
@@ -1045,6 +1045,7 @@ aclMatchProxyAuth(wordlist * data, const char *proxy_auth, acl_proxy_auth_user *
            /* password was checked and did match */
            debug(28, 4) ("aclMatchProxyAuth: user '%s' validated OK\n", user);
            /* store validated user in hash, after filling in expiretime */
+           xstrncpy(checklist->request->user_ident, user, USER_IDENT_SZ);
            auth_user->expiretime = current_time.tv_sec + Config.authenticateTTL;
            hash_join(proxy_auth_cache, (hash_link *) auth_user);
            /* Continue checking below, as normal */