[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Strange nisMapEntry

Hi David,

are you having that for your olcAccess Attrs too? (for ACLs)

# {0}config, config
dn: olcDatabase={0}config,cn=config
objectClass: olcDatabaseConfig
olcDatabase: {0}config
olcAccess:: ezB9dG8gKiBieSBkbi5leGFjdD1jbj1sb2NhbHJvb3QsY249Y29uZmlnIG1hbmFnZS
olcRootDN: cn=config

I got that too, maybe its set for security reasons to not use some holes in the ACLs.
I don't know whats in your nismapentry as value, but maybe its for the same reason.

Just a thought from a bloody openldap newb :)


On Wed, Feb 10, 2010 at 19:01, David LEROUX <elhijo.mgl@gmail.com> wrote:
Hi all,
I have in my ldifs, whatever the way I do them (slapcat ldapsearch -LLL...) some strange entry, like if it was hashed.

Here is a sample:
nisMapEntry:: LXJ3LHRjcCxpbnRyLHJzaXplPTMyNzY4LHdzaXplPTMyNzY4LHRpbWVvPTUwLHJldHJhbnM9MTAgeWFrMjA6L3VzcjIvdXNlcnMvJiA=
Which should be:
nisMapEntry: -rw,tcp,intr,rsize=32768,wsize=32768,timeo=50,retrans=10 yak20:/usr2/users/&

If I re import them from a fresh "normal" ldif generated from my nis automount maps, it does the same, it's alway the same affected entries...
In phpldapadmin I can see it well, but not in my ldifs and its a bit annoying for me...
Any idea ?

David Leroux


Ted Turner  - "Sports is like a war without the killing."