Geek Answers Handbook

Why doesn't ValidateUser return anymore?

I am using the standard .NET membership provider and I think I will see if anyone can highlight it.

A call to ValidateUser returns true or false. Now, since the method accepts a username and password, one would assume that the return result would display an invalid username or password. But if we delve into this, we find that it also checks IsLockedOut and IsApproved.

public override bool ValidateUser (string username, string password)
{
    MembershipUser user = GetUser (username, false);
    /* if the user is locked out, return false immediately */
    if (user.IsLockedOut)
        return false;
    /* if the user is not yet approved, return false */
    if (!user.IsApproved)
        return false;
    ......

In my application, I would like to use IsApproved for my own means. Just switching my own provider will not work, because I'm still limited to the result of bool. Creating a user gives us all the information we need, so why not ValidateUser? Did I miss something?

+5
1

, , , - - , .

, , .

№1: "Admin" "", "". , , , Admin/Password .

№ 2: "Admin" "", , . , , .

№ 3: "Admin" "", , . , "" . - , , , - .

№4: "Admin" "", , . . .

, beans , , , chatty systems, , .

, .

+9

More articles:


All Articles