I am encountering a problem with v.6.2.1 in relation with the new MembersMembershipProvider. I am upgrading a 6.1 website to 6.2 (where the new member provider has been introduced) and seeing various Exceptions coming up when I create members through the API.

The code I use looks as follows:

UmbracoMembershipProviderBase provider = (UmbracoMembershipProviderBase)Membership.Providers["UmbracoMembershipProvider"];
var mt = new MemberType(1093);

MembershipCreateStatus createStatus = new MembershipCreateStatus();
MembershipUser membershipUser = provider.CreateUser(mt.Alias,
                                                    userName, password, emailAdj,
                                                    "empty", "empty", true,
                                                    null, out createStatus);

You must specify a non-autogenerated machine key to store passwords in the encrypted format. Either specify a different passwordFormat, or change the machineKey configuration to use a non-autogenerated decryption key.

The error occurs in:

- StackTrace:
  at System.Web.Security.MembershipProvider.EncryptPassword(Byte[] password, MembershipPasswordCompatibilityMode legacyPasswordCompatibilityMode)
  at Umbraco.Web.Security.Providers.UmbracoMembershipProvider`2.EncryptString(String str)
  at Umbraco.Web.Security.Providers.UmbracoMembershipProvider`2.PerformCreateUser(String memberTypeAlias, String username, String password, String email, String passwordQuestion, String passwordAnswer, Boolean isApproved, Object providerUserKey, MembershipCreateStatus& status)
..
etc

I never had to provide a machine key for generating a password hash (on 6.1 and older) so this seems very strange.

Still stranger: although none of the created members are visible in the Members section of the umbraco backoffice; members do seem to be added to the repository. I indeed also have this utility to update members and when I run this subsequently (with the members that could not be created) all members indeed appear in the backoffice. No exception occurs then.

By the way: the same exception comes up when using the asp.net 'standard' provider method to create a user (i.e. not using the cast).

Any idea?