Customize Login Control

[Andrew Hayes]

Added the Login and ValidationSumma ry controls to the default.aspx page of
VS2005 web application. Set the DestinationPage URL to a different "members
only" page, OnAuthenticate to my custom Authenticate event, and
MembershipProvi der to my custom provider.

Converted the Login control to a Template and added an additional <asp:Label
AssociatedContr olID=Department ...>Department, <asp:TextBox ID=Department
....and <asp:RequiredFi eldValidator ControlToValida te=Department ...so I
now have 3 fields to fill in to login. If I don't, the ValidationSumma ry
control correctly identifies the problem so that all seems to be working.

Created my own Membership Provider, and included a ValidateUser method with
3 string parameters (as well as the usual 2 parameter override), which I
call from the Login1_Authenti cate event.

Trouble is, I can't seem to get the 2 things to work together.

If I remove the OnAuthenticate then it correctly goes to the
ValidateUser(st ring, string) of my custom Provider, but if I include the
OnAuthenticate then it goes to the event OK, but how do I call the custom
ValidateUser method?

Hopefully someone can post the code that goes in the event -

protected void Login1_Authenti cate(object sender, AuthenticatedEv entArgs e)
{
/* Authenticate using myProvider.Vali dateUser(userNa me, password,
department) somehow? */
}

[Andrew Hayes]

A bit more info. This is what the code looks like if I use the normal 2
parameter method for authenticating the users:

protected void Login1_Authenti cate(object sender, AuthenticatedEv entArgs e)
{
e.Authenticated = Membership.Vali dateUser(Login1 .UserName,
Login1.Password );
}

That works fine, and I know it uses the overriden ValidateUser in my custom
provider as it hits the breakpoint there, but what I really want it to say
is:

protected void Login1_Authenti cate(object sender, AuthenticatedEv entArgs e)
{
e.Authenticated = MyMembership.Va lidateUser(Logi n1.UserName,
Login1.Password , Login1.Deparmen t);
}

But that generates an error. MyMembership doesn't exist in the current
context. OK, so lets change it to Membership then... Another error. The
Login control does not contain a definition for Department. OK, so I replace
Login1.Departme nt with "test" and try again. This time I get a No overload
for ValidateUser takes 3 arguments. Drop the 3rd argument and I'm back to
the working 2 parameter version.

It's probably very simple, but even google doesn't find an appropriate
example.