MultiTenant does not initialize properly

[codingoutloud]

Running a fresh installation of MembershipReboot results in a call to

UserAccountService.CreateAccount(username, password, email)

Which is a pass-thru to another overloaded CreateAccount method, passing through all parameters and adding a null value for tenant.

If SecuritySettings.Instance.MultiTenant is true then the tenant value will be null. Then there is a check to ensure it is not null:

if (String.IsNullOrWhiteSpace(tenant)) throw new ArgumentException("tenant");

Under a multi-tenant configuration, this exception will be triggered always.

[brockallen]

Sure, and that's by design. If you notice almost every other API works that way. Multi-tenant is a major setting and should be decided upon ahead of time for the app. It really affects how all the APIs are invoked such that if it's set to true then the app should never use the APIs that don't accept the tenant and instead should always pass it. The sample app is not meant to be multi-tenant so I don't think this is an issue.

Perhaps what we really need is another sample that shows what some of the differences would be for a multi-tenant app. The problem with a multi-tenant app is that everyone always has different requirements for where the tenant comes from. I'm not sure how to express that in a sample.