Re: [Cpu-users] New entries uses 'cn'.
                
                Brought to you by:
                
                    matheny
                    
                
            
            
        
        
        
    | 
     
      
      
      From: Blake M. <bma...@pu...> - 2003-09-16 23:37:17
      
     
   | 
This is fixed in CVS (check out the CVS copy if you need it right now, a temporary fix is to specify -A uid at the command line). Expect a 1.4.1 release by Monday. Some patches have come in along with some bug reports. -Blake Whatchu talkin' 'bout, Willis? > > We are trying to use the 'cpu' utility to manage a ldap server (having > gone through a few web based versions). Our dn for each user will have > the form of dn: uid=<username>,ou=People,dc=xyz,..., but when I use > the cpu utility the dn is created as dn: > cn=<username>,ou=People,dc=xyz. > > > > This is the config file: > > [LDAP] > LDAP_HOST = 127.0.0.1 > LDAP_PORT = 389 > # Can also use LDAP_URI = [1]ldaps://localhost:389 for TLS support > BIND_DN = cn=Manager,dc=.... > > BIND_PASS = > > USER_BASE = ou=People,dc=... > GROUP_BASE = ou=Group,dc=... > USER_OBJECT_CLASS = posixAccount,shadowAccount,top > GROUP_OBJECT_CLASS = posixGroup,top > USER_FILTER = (objectClass=posixAccount) > GROUP_FILTER = (objectClass=posixGroup) > USER_CN_STRING = uid > GROUP_CN_STRING = cn > > > > This looks OK to me, including the USER_CN_STRING, which I have se to > uid instead of cn. > > > > Your help is appreciated. > > > > Thx, > > Hans E. > > References > > 1. ldaps://localhost:389/ -- Blake Matheny "... one of the main causes of the fall of the bma...@pu... Roman Empire was that, lacking zero, they had http://www.mkfifo.net no way to indicate successful termination of http://ovmj.org/GNUnet/ their C programs." --Robert Firth  |