From b1dabb11333a715b0e23e91eecaf29933ea383a7 Mon Sep 17 00:00:00 2001 From: Endi Sukma Dewata Date: Wed, 9 Sep 2009 12:45:24 -0400 Subject: s4: Use SASL authentication against Fedora DS. 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 --- source4/setup/fedorads-sasl.ldif | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 source4/setup/fedorads-sasl.ldif (limited to 'source4/setup/fedorads-sasl.ldif') diff --git a/source4/setup/fedorads-sasl.ldif b/source4/setup/fedorads-sasl.ldif new file mode 100644 index 0000000000..99bb6a72cd --- /dev/null +++ b/source4/setup/fedorads-sasl.ldif @@ -0,0 +1,9 @@ +# Map samba-admin to CN=samba-admin,${SAMBADN} +dn: cn=samba-admin mapping,cn=mapping,cn=sasl,cn=config +objectClass: top +objectClass: nsSaslMapping +cn: samba-admin mapping +nsSaslMapRegexString: ^samba-admin$ +nsSaslMapBaseDNTemplate: CN=samba-admin,${SAMBADN} +nsSaslMapFilterTemplate: (objectclass=*) + -- cgit