summaryrefslogtreecommitdiff
path: root/source4/setup/secrets_init.ldif
AgeCommit message (Collapse)AuthorFilesLines
2009-11-24s4:provision Move secrets.ldb over to .c file module lists, like sam.ldbAndrew Bartlett1-1/+1
2009-11-24s4:provision Remove 'operational' from secrets.ldb module listAndrew Bartlett1-1/+1
2009-10-23s4:setup Mark 'cn' in secrets as case insensitiveAndrew Bartlett1-0/+1
While this does not matter very much, others may later expect 'cn' to be case insensitive. Andrew Bartlett
2008-07-15Connect to the LDAP backend with SASL credentials.Andrew Bartlett1-1/+1
This reworks our LDAP backend code to move from anonymous access to a shared-secret SASL-protected connection. (SASL selects NTLM or DIGEST-MD5 on my system). To get this working, we must pre-populate the LDAP backend with a DN to store ths SASL secret on, and we use back-ldif for this. This gives us a reasonable basis to deploy a replicated OpenLDAP backend solution. Andrew Bartlett (This used to be commit cd0745253c4a9ec59a035e830e54d74a05b71aaa)
2007-10-10r21135: Instead of having hooks to update keytabs as an explicit thing, updateAndrew Bartlett1-0/+15
them as a hook on ldb modify, via a module. This should allow the secrets.ldb to be edited by the admin, and to have things update in the on-disk keytab just as an in-memory keytab would. This isn't really a dsdb plugin, but I don't have any other good ideas about where to put it. Andrew Bartlett (This used to be commit 6ce557a1aff4754d2622be8f1c6695d9ee788d54)