G
Guest
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!
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!