No author problem for svn server

[wan...@htche.com]

Hi there,
I'm recently encounting a weird problem, not sure when it started, my svn 
server doesn't log the author when committing. We are a team, but it forgets 
most of the members, only one person exception, there's no different between 
this person and others. though every one is able to access and commit as usual, 
My svn server authenticates against LDAP and no anonymous access allowed. here 
is the config and log:
--

  ServerAdmin svnad...@abc.com

  DocumentRoot /var/www/svn

  ServerName svn.abc.com

  ErrorLog logs/svn.int.abc.com-error_log

  CustomLog logs/svn.int.abc.com-access_log common



  

    

      DAV svn

      SVNParentPath /var/www/svn

      SVNReposName "Subversion Repository"



      # SSLRequireSSL

      AuthBasicProvider ldap

      AuthType Basic

      AuthzLDAPAuthoritative on

      AuthName "Authorization Realm"

      AuthLDAPURL 
"ldaps://ldap.abc.com/ou=people,dc=abc,dc=com?uid?sub?(objectClass=*)" NONE

      AuthLDAPBindDN uid=svnadmin,ou=people,dc=abc,dc=com

      AuthLDAPBindPassword RjOmm4JIM8VNuecbw7xZ       

        Require valid-user

        require ldap-group cn=svnusers,ou=groups,dc=abc,dc=com

        AuthLDAPGroupAttribute memberUid

        AuthLDAPGroupAttributeIsDN off

      

    

  





$ svn log...r12 | (no author) | 2015-02-12 10:33:15 +0800...

Do I forget anything?
Jeff

Re: Re: Aw: No author problem for svn server

[wan...@htche.com]

That's what I'm doing right now. thank you Andreas
Jeff


 From: Andreas StiegerDate: 2015-03-21 16:04To: usersCC: 
wangji@htche.comSubject: Re: Aw: No author problem for svn serverHi,
 
On 20/03/15 16:54, Andreas Stieger wrote:
> Your configuration requires a password for reading, but everyone (!) can 
> commit.
> This should be the other way around, e.g.
> 
> 
> See https://subversion.apache.org/faq.html#no-author why you have no author 
> without auth challenge.
 
I would like to pre-empt Jeff's question brought to me privately:
To require authentication for ALL operations, which one can assume is
desired for a corporate deployment, simply do not wrap in   and
 at all, this making the "Require valid-user" requirement
effective for all requests. You may refer to the Apache httpd
documentation for detail on this.
 
Andreas