s4:setup Don't manually set @ATTRIBUTES any more

We now set these as part of the schema load, and we now load the
schema before the provision loads the DB, so setting them here is
pointless

Andrew Bartlett

diff --git a/source4/setup/provision_init.ldif b/source4/setup/provision_init.ldif
index 8e9b68fb306fc4280bf85433e83208c9258e114a..e2e7d096af0d819eb0612c1c21a39443fa27f494 100644 (file)
--- a/source4/setup/provision_init.ldif
+++ b/source4/setup/provision_init.ldif
@@ -1,35 +1,3 @@
-#These attributes are only used as far as the bootstrapping of the
-# schema.  After that, the attributes from the schema are used.
-#
-# Therefore, they must strictly match the schema
-
-dn: @ATTRIBUTES
-userPrincipalName: CASE_INSENSITIVE
-servicePrincipalName: CASE_INSENSITIVE
-dnsDomain: CASE_INSENSITIVE
-dnsRoot: CASE_INSENSITIVE
-nETBIOSName: CASE_INSENSITIVE
-cn: CASE_INSENSITIVE
-dc: CASE_INSENSITIVE
-name: CASE_INSENSITIVE
-lDAPDisplayName: CASE_INSENSITIVE
-subClassOf: CASE_INSENSITIVE
-dn: CASE_INSENSITIVE
-sAMAccountName: CASE_INSENSITIVE
-objectClass: CASE_INSENSITIVE
-userPassword: HIDDEN
-krb5Key: HIDDEN
-ntPwdHash: HIDDEN
-sambaNTPwdHistory: HIDDEN
-lmPwdHash: HIDDEN
-sambaLMPwdHistory: HIDDEN
-createTimestamp: HIDDEN
-modifyTimestamp: HIDDEN
-groupType: INTEGER
-sAMAccountType: INTEGER
-systemFlags: INTEGER
-userAccountControl: INTEGER
-
 dn: @OPTIONS
 checkBaseOnSearch: TRUE