https://issues.apache.org/bugzilla/show_bug.cgi?id=57203

--- Comment #2 from Jorgen <[email protected]> ---
(In reply to Eric Covener from comment #1)
> There is a fix in 2.4.11 that may be related, but tough to tell w/o context:
> 
>   *) mod_ldap: In 2.4.10, some LDAP searches or comparisons might be done
> with
>      the wrong credentials when a backend connection is reused.
> 
> Can you get it to fail under loglevel debug or trace8?
> 
> Otherwise you are right that you should just see a retry and maybe a short
> delay if a connection in the pool goes south.



I have logs from Subversion edge in debug mode (I think thats trace8)

[Thu Nov 06 09:44:54.159442 2014] [ssl:debug] [pid 23265]
ssl_engine_kernel.c(236): [client 10.249.66.28:49770] AH02034: Subsequent
(No.2) HTTPS request received for child 1 (server svn-it.got.company.net:443)
[Thu Nov 06 09:44:54.159483 2014] [authz_core:debug] [pid 23265]
mod_authz_core.c(799): [client 10.249.66.28:49770] AH01626: authorization
result of Require valid-user : denied (no authenticated user yet)
[Thu Nov 06 09:44:54.159488 2014] [authz_core:debug] [pid 23265]
mod_authz_core.c(799): [client 10.249.66.28:49770] AH01626: authorization
result of <RequireAny>: denied (no authenticated user yet)
[Thu Nov 06 09:44:54.159560 2014] [authnz_ldap:debug] [pid 23265]
mod_authnz_ldap.c(515): [client 10.249.66.28:49770] AH01691: auth_ldap
authenticate: using URL
ldaps://vds.company.biz:636/ou=Internal,ou=Users,o=XXX?uid?sub
[Thu Nov 06 09:44:54.161569 2014] [authnz_ldap:info] [pid 23265] [client
10.249.66.28:49770] AH01695: auth_ldap authenticate: user userX authentication
failed; URI /svn/some-path/pom.xml [User not found][No such object]
[Thu Nov 06 09:44:54.161580 2014] [auth_basic:error] [pid 23265] [client
10.249.66.28:49770] AH01618: user userX not found:
/svn/EIE/!svn/rvr/452/some-path/pom.xml

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to