summaryrefslogtreecommitdiff
path: root/source4/setup/fedorads-samba.ldif
AgeCommit message (Collapse)AuthorFilesLines
2009-11-02s4 - SID allocation using FDS DNA pluginEndi S. Dewata1-0/+10
2009-11-02s4 - Mapped AD schema to existing FDS schema.Endi S. Dewata1-0/+1
2009-09-10s4: Use SASL authentication against Fedora DS.Endi Sukma Dewata1-0/+10
1. During instance creation the provisioning script will import the SASL mapping for samba-admin. It's done here due to missing config schema preventing adding the mapping via ldapi. 2. After that it will use ldif2db to import the cn=samba-admin user as the target of SASL mapping. 3. Then it will start FDS and continue to do provisioning using the Directory Manager with simple bind. 4. The SASL credentials will be stored in secrets.ldb, so when Samba server runs later it will use the SASL credentials. 5. After the provisioning is done (just before stopping the slapd) it will use the DM over direct ldapi to delete the default SASL mappings included automatically by FDS, leaving just the new samba-admin mapping. 6. Also before stopping slapd it will use the DM over direct ldapi to set the ACL on the root entries of the user, configuration, and schema partitions. The ACL will give samba-admin the full access to these partitions. Signed-off-by: Andrew Bartlett <abartlet@samba.org>