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

Re: Problem with olcAccess



Hi Tobias,

It looks like it's simply base64 encoded. Did you have any trailing whitespace after your olcAccess entry? As far as I'm aware the rule will still be processed correctly although I'm happy to be corrected if this isn't the case.

Cheers,

Mark

On 22/09/12 13:47, Tobias Hachmer wrote:
Hello list,

I simply trying to add an olcAccess entry to the config backend.

here the file contents:

dn: olcDatabase={1}hdb,cn=config
changeType: modify
add: olcAccess
olcAccess: to dn.subtree="ou=public,ou=addressbook,dc=example,dc=com" by
users write

What I've get after adding this to the backend is:

olcAccess: {0}to attrs=userPassword,shadowLastChange by self write by
dn="cn=a
  dmin,dc=example,dc=com" write by * none
olcAccess: {1}to dn.base="" by * read
olcAccess: {2}to * by self write by dn="cn=admin,dc=example,dc=com"
write by *
   read
olcAccess::
ezN9dG8gZG4uc3VidHJlZT0ib3U9cHVibGljLG91PWFkZHJlc3Nib29rLGRjPWtva2
  VsbmV0LGRjPWRlIiBieSAqIHdyaXRlIA==

What's going on here, what did I wrong, I didn't get it yet. Please help
me.

Regards,
Tobias Hachmer




--
/****************************

Mark Cairney
ITI UNIX Section
Information Services

Tel: 0131 650 6565
Email: Mark.Cairney@ed.ac.uk

****************************/

The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.