Customized Membership Provider

[=?Utf-8?B?SGFyZHkgV2FuZw==?=]

Hi all,
We currently have our own customer/login tables in our database linked with
CustomerID columns of both tables. Some of the requirements of the system are

1) When I validate users, I need to pass more parameters than just
username/password, for example customers are created for different clients,
so I need to pass our ClientID with username/password together. We build one
portal to support multiple clients.

2) When a customer is validated, I need to get CustomerID instead of
username from Context.User.Identity.

By implementing MembershipProvider class, I don't think I can achieve any of
requirement mentioned above. Do I miss something or there are some other
tricks I don't know?

Thanks for any suggestions or comments!
--
Regards
Hardy

[=?Utf-8?B?UGV0ZXIgQnJvbWJlcmcgW0MjIE1WUF0=?=]

You can certainly implement what you describe, you will need to write a
custom MembershipProvider that derives from the ProviderBase class.
There is plenty of sample code around for implementing custom Membership,
Profile, and Roles providers.
Peter

--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net


"Hardy Wang" wrote:

Hi all,
We currently have our own customer/login tables in our database linked with
CustomerID columns of both tables. Some of the requirements of the system are

1) When I validate users, I need to pass more parameters than just
username/password, for example customers are created for different clients,
so I need to pass our ClientID with username/password together. We build one
portal to support multiple clients.

2) When a customer is validated, I need to get CustomerID instead of
username from Context.User.Identity.

By implementing MembershipProvider class, I don't think I can achieve any of
requirement mentioned above. Do I miss something or there are some other
tricks I don't know?

Thanks for any suggestions or comments!
--
Regards
Hardy

[=?Utf-8?B?SGFyZHkgV2FuZw==?=]

Sorry, I implemented MembershipProvider class, ValidateUser only accepts 2
parameters, but I need more.

public override bool ValidateUser(string username, string password) {
}

How can I do it?

Let me do a search around.
--
Regards
Hardy
"Peter Bromberg [C# MVP]" wrote:

You can certainly implement what you describe, you will need to write a
custom MembershipProvider that derives from the ProviderBase class.
There is plenty of sample code around for implementing custom Membership,
Profile, and Roles providers.
Peter

--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net


"Hardy Wang" wrote:

Hi all,
We currently have our own customer/login tables in our database linked with
CustomerID columns of both tables. Some of the requirements of the system are

1) When I validate users, I need to pass more parameters than just
username/password, for example customers are created for different clients,
so I need to pass our ClientID with username/password together. We build one
portal to support multiple clients.

2) When a customer is validated, I need to get CustomerID instead of
username from Context.User.Identity.

By implementing MembershipProvider class, I don't think I can achieve any of
requirement mentioned above. Do I miss something or there are some other
tricks I don't know?

Thanks for any suggestions or comments!
--
Regards
Hardy

[=?Utf-8?B?UGV0ZXIgQnJvbWJlcmcgW0MjIE1WUF0=?=]

How about we create a ValidateUserEx method that accepts all your parameters,
and you forward the call with the username, password to the overridden base
class method?
Peter

--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net


"Hardy Wang" wrote:

Sorry, I implemented MembershipProvider class, ValidateUser only accepts 2
parameters, but I need more.

public override bool ValidateUser(string username, string password) {
}

How can I do it?

Let me do a search around.
--
Regards
Hardy
"Peter Bromberg [C# MVP]" wrote:

You can certainly implement what you describe, you will need to write a
custom MembershipProvider that derives from the ProviderBase class.
There is plenty of sample code around for implementing custom Membership,
Profile, and Roles providers.
Peter

--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net


"Hardy Wang" wrote:

Hi all,
We currently have our own customer/login tables in our database linked with
CustomerID columns of both tables. Some of the requirements of the system are
>
1) When I validate users, I need to pass more parameters than just
username/password, for example customers are created for different clients,
so I need to pass our ClientID with username/password together. We build one
portal to support multiple clients.
>
2) When a customer is validated, I need to get CustomerID instead of
username from Context.User.Identity.
>
By implementing MembershipProvider class, I don't think I can achieve any of
requirement mentioned above. Do I miss something or there are some other
tricks I don't know?
>
Thanks for any suggestions or comments!
--
Regards
Hardy