Hi all,

I've installed the External Database Provider and am stepping through code, hitting the right points, and I've determined that it's successfully validating our users against the external database - which is great (I suspect the problem I'm having is actually with DNN, but you guys will probably be able to tell me).

Even though I'm validating against the external database, I still can't log in. The provider is unable to create the user account in DNN. When it calls UserController.CreateUser, I'm getting back a UserCreateStatus.InvalidPassword status.

Now, our passwords in our external database are encrypted, so they look something like this:

AA30BD02E4F5CE2769B6625E796868B52F091514

So it's a string like that which it's trying to set the password to on the user object.

What I'm suspecting, is that DNN receives this, does its own encryption on that string, and ends up with something too big for the password column in the DNN database.

So, does this sound plausible, or is it something else?

My solution to the problem is to just amend the provider to hard code the imported password (to DateTime.Now.Ticks.ToString()). I figure it doesn't matter what the password is of the user account in DNN since it will never get tested anyway. We're always going to rely on the external database (if that's unavailable, DNN *has* to be unavailable too).

Am I missing something very obvious...?

Cheers,

Tom