r8790: Finish the migration of aliases and privilages with SamSync, by adding

templating support for foreignSecurityPrincipals to the samdb module.
This is an extension beyond what microsoft does, and has been very
useful :-)

The setup scripts have been modified to use the new template, as has
the SAMR and LSA code.

Other cleanups in LSA remove the assumption that the short domain name
is the first component of the realm.

Also add a lot of useful debug messages, to make it clear how/why the
SamSync may have gone wrong.  Many of these should perhaps be hooked
into an error string.

Andrew Bartlett
(This used to be commit 1f071b0609c5c83024db1d4a7d04334a932b8253)

1 files changed, 4 insertions, 2 deletions

diff --git a/source4/setup/provision b/source4/setup/provision
index 90363fcf20..dc542f59f0 100755
--- a/source4/setup/provision
+++ b/source4/setup/provision
@@ -27,7 +27,8 @@ ok = GetOptions(ARGV, options,
 		'nogroup=s',
 		'wheel=s',
 		'users=s',
-		'quiet');
+		'quiet',
+                'blank');
 if (ok == false) {
    println("Failed to parse options: " + options.ERROR);
    return -1;
@@ -72,6 +73,7 @@ provision [options]
  --wheel	GROUPNAME	choose 'wheel' privileged group
  --users	GROUPNAME	choose 'users' group
  --quiet			Be quiet
+ --blank			do not add users or groups, just the structure
 
 You must provide at least a realm and domain
 
@@ -106,6 +108,6 @@ for (r in options) {
 
 message("Provisioning for %s in realm %s\n", subobj.DOMAIN, subobj.REALM);
 message("Using administrator password: %s\n", subobj.ADMINPASS);
-provision(subobj, message);
+provision(subobj, message, options["blank"] != undefined);
 message("All OK\n");
 return 0;