search for: ldapbase

I am trying to get puppet to manage my LDAP users but I don''t appear to be having much success. What I have in puppet.conf is this [puppetmasterd] ldapserver=ldap.myorg.company.com ldapbase=dc=myorg,dc=org ldapuser=cn=admin,dc=myorg,dc=org ldappassword=mysecret ldapparentattr=dc=myorg,dc=org I added the ldapparentattr in desperation and doubt if it''s actually required. Now I have a class which says user { "myuser": u...

hi dovecot list help me please dovecot-1.0.r27 exim lda virtual users in ldap base i decided to start using the sieve pluging so i have to make the homes (now my homeDirectory in ldapbase is /nonexistent). there is a lot of users, so i dont wonna to make changes in every ldap record + imho the hard link to userhome in ldap - its a not good idea. so is there any way to make it easy? may be like home_location = bla-bla-bla/%n/home in dovecot.conf (or in dovecot-ldap.conf ) sor...

...warning on external node support here but after a recent upgrade for my puppetmaster I get: puppetmasterd[19397]: Could not find aa0-006-4.foo.com with names aa0-006-4.foo.com, aa0-006-4 I''ve not changed puppetd.conf which contains: ldapnodes = true ldapserver = my.ldap.foo.com ldapbase = ou=hosts,dc=foo,dc=com I''ve not explicitly set external_nodes (so it stays false). What else needs to be done? Cheers, Ryan

...dpa2kgYW5kIFJUIGJveCA= l: statcomp puppetclass: default puppetclass: test puppetclass: solaris puppetclass: solaris10 puppetclass: statcomp # search result search: 2 result: 0 Success I then tried to modify puppet.conf to point to LDAP using the following lines: ldapserver = ldapdev1.domain.com ldapbase = dc=puppet ldapnodes = true I restarted puppermasterd, but now I am getting this error on the puppermaster host as well as the puppet client host. err: Could not find sink.domain.com with names sink.domain.com, sink I pasted relavent debug information from the puppetmasterd and puppetd at: http...

I am trying to configure puppet with LDAP repository . I have set puppet schema and I have also added node definition at LDAP. Here is my configuration details . ############################################################## Puppet.conf node_terminus = ldap ldapserver = 10.250.11.127 ldapbase = ou=Hosts,dc=xyz,dc=com ldapassword = secret ############################################################# Node details #################### # extended LDIF # # LDAPv3 # base <dc=xyz,dc=com> with scope sub # filter: (objectclass=*) # requesting: ALL # # xyz.com dn: dc=xyz,dc=com object...

...t;ldapmigrate" script and changed all occurances of "Group" to "Groups" for naming consistancy and to match the defaults of the LDAP Account Manager. Then do the migration... LDAPBIND="cn=root,dc=precidia" LDAPPASS="secret" LDAPBASE="dc=precidia" LDAPHOST="localhost" ldapmigrate -D $LDAPBIND -w $LDAPPASS -b $LDAPBASE -h $LDAPHOST --extschema --extconts --prepdb ldapmigrate -D $LDAPBIND -w $LDAPPASS -b $LDAPBASE -h $LDAPHOST --extschema --minuid=1001 --mingid=1000 -f /etc/passwd...

...ple.com, host2.example.net.example.com --- Maybe Puppetmaster was loaded "cn=host1.example.net" and "dc=example,dc=com". Puppetmaster and LDAP Server Config, puppet.conf --- [main] node_terminus = ldap ldapserver = 192.168.0.101 ldapport = 389 ldapbase = ou=Servers,dc=puppet,dc=sf ldapstring = (&(objectclass=puppetClient)(cn=%s)) ldapuser=cn=Manager,dc=example,dc=com ldappassword=******* --- host1.ldif --- dn: cn=host1.example.net, ou=servers, dc=example, dc=com objectClass: device objectClass: puppetClient objectC...

With both puppet-0.23.0 and 0.23.1 if I setup just the configuration file puppet.conf, none of the puppetd options seem to get parsed. I first noticed this when monit failed to start/stop services due to the lack of a pid file being generated (and mine is not in one of the usual places). I''m sure that something like the patch attached but I bet it breaks other assumptions :-) Cheers,

...about SID stuff. Try some googling on secrets.tdb or just throw secrets.tdb away if it's just a test setup, it's in /var/lib/samba or /var/samba. Hope this is helpfull, I have had similar error messages in winxp for some time but with me someone pointed me at nss not looking in the right ldapbase, but that's not your problem, i just mentioned it for people searching the sambalist history. Regards Bas

...., no connections to the ldap server). I *did* update the puppetmasterd conf, adding the variable "node_terminus = ldap" since that apparently changed between versions. Here are all three entries: # LDAP Config node_terminus = ldap ldapserver = ldap.<some_domain>.com ldapbase = ou=nodes,dc=<domain>,dc=com Like I said, this was working great before. If it makes a difference, when I upgraded to 0.25, I also switched to a Mongrel configuration. From the client side, I see this, but I am not sure if it is a problem: debug: Failed to load library ''ldap'...

...ygem-activeresource-2.1.1-1.el5 rubygem-activesupport-2.1.1-2.el5 rubygem-activerecord-2.1.1-2.el5 rubygems-1.3.1-1.el5 rubygem-rails-2.1.1-2.el5 ruby-1.8.5-5.el5_4.8 ruby-mysql-2.7.3-1.el5 And the puppetmaster config : [puppetmasterd] node_terminus = ldap ldapserver = nsldap.ircam.fr ldapbase = ou=Hosts,dc=ircam,dc=fr modulepath = /etc/puppet/modules:/usr/share/puppet:/var/lib/puppet/modules storeconfigs = true dbserver = mysql2.ircam.fr dbadapter = mysql dbname = XXXXXXXXXXXXXXXX dbuser = XXXXXXXXXXXXXXXX dbpassword = XXXXXXXXXXXXXXXXXXXXXXXXXXX report...

I use a openLDAP database for authentication on my Redhat 7.2 server. The domain is "HOME". I have had no problem adding trust accounts and authenticating against it. Today I had to change the name of my Win2K workstation from poseiden to poseiden1 for compatibility with a package I am testing. Once I changed it and put in a new trust account, I could not rejoin the domain. I gave up and

...source = puppet://$server/plugins plugindest = $vardir/lib/puppet factpath = $vardir/lib/facter environment = production [puppetmasterd] environments = production,testing storeconfigs=true smtpserver = smarthost dbadapter = mysql dbserver = lhr1-ahbat-01 ldapnodes = true ldapserver = lhr1-ahaaa-02 ldapbase = ou=Hosts,dc=active,dc=com dbname = puppet dbuser = puppetuser dbpassword = ******* reports = log,store,tagmail syslogfacility = user tagmap = /etc/puppet/tagmail.conf [puppetd] server=lhr1-ahbat-01 pluginsync=true report=true [testing] modulepath=$confdir/modules-testing [production] modulepat...

...by the client) I notice that the environment variable LOGONSERVER is still set to the name of the old server. That may just be part of the caching, however - I'm not sure. Any ideas on what I should do? Do I need to change the sambaSID entry in the sambaDomainName=<DOMAIN>,<LDAPBASE> entry of my ldap server? Included here is a copy of my smb.conf, if that helps. > [global] > workgroup = <DOMAIN> > realm = <DOMAIN> > server string = Fileserver > map to guest = Bad User > # smb passwd file = /etc/samba/p...

...http.log ignorecache = false ignoreimport = false ignoreschedules = false inventory_port = 8140 inventory_server = puppet inventory_terminus = facter keylength = 1024 lastrunfile = /var/lib/puppet/state/last_run_summary.yaml lastrunreport = /var/lib/puppet/state/last_run_report.yaml ldapattrs = all ldapbase = "" ldapclassattrs = puppetclass ldapnodes = false ldapparentattr = parentnode ldappassword = "" ldapport = 389 ldapserver = ldap ldapssl = false ldapstackedattrs = puppetvar ldapstring = (&(objectclass=puppetClient)(cn=%s)) ldaptls = false ldapuser = "" lexical =...

Can someone explain to me the mechanizm that Samba uses to relate Machines to Users? I am trying to set up a Samba-LDAP PDC and it seems to work OK but I get "No mapping between account names and security IDs was done." This would seem to be a simple user/group ownership/permissions thing. Now I have the following potentially pertinent ou's: People Computers Groups One

We are implementing the following: Solaris 9 iPlanet Directory Server 5.1 (bundled with Solaris 9) openldap 2.1.16 Only used for ldap libaries (samba will not compile without. Is this other people's experience?) samba 2.2.8 compiled with ./configure --with-ldapsam --with-acl-support We have the samba server acting as a PDC with all user and machine accounts in LDAP as

...mote server: Error 400 on SERVER: Failed when searching for node ubuntu5.ttinet: LDAP Search failed on the puppet master... puppet.conf [master] # ENC (external node classificiations) node_terminus = ldap ldapnodes = true ldapclassattrs = puppetclass # LDAP ldapserver = ubuntu.ttinet ldapbase = ou=Hosts,dc=ttinet,dc=local ldapuser = cn=admin,dc=ttinet,dc=local ldappasswd = XXXXXXXXXXXX ldapstring = (&(objectclass=puppetClient)(cn=%s)) ldaptls = false ldapssl = false ldapport = 389 and this is a piece of cake from CLI # ldapsearch -x ''(&(objectclass=puppetC...

Hi all, This just keeps coming up, again and again, so I decided to take a few hours and break everyone''s configuration. Oh, wait, just kidding. :) Really, I''ve completely rewritten external node support. Here''s the changelog entry: Only ONE node source can be used -- you can use LDAP, code, or an external node program, but not more than one.

...LDAP searches. It''s impossible to provide # a meaningful default here, although the LDAP libraries might # have one already set. Generally, it should be the ''ou=Hosts'' # branch under your main directory. # The default value is ''''. # ldapbase = # Whether SSL should be used when searching for nodes. # Defaults to false because SSL usually requires certificates # to be set up on the client side. # ldapssl = false # The LDAP port. Only used if `ldapnodes` is enabled. # The default value is ''389''...