Re: Membership Services and Client Logins?

The Membership bits are primarily authentication, not authorization. You can take care of authorization with roles.

With what you are stating, you might be better extending the Membership bits with a custom provider, to segregate customer data so it can work with multiple user accounts. Add an account table, for example, and create an account for the first user to sign up under customer X. You then have to alter the sign up procedure or create an admin page for the customer to add log ins. This is not all handled by any of the bits in Membership.

Personally, I would not go towards profiles. They are okay for personalization, but do not make a good authorization piece.

--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA

Subscribe to my blog
http://gregorybeamer.spaces.live.com/lists/feed.rss

or just read it:
http://gregorybeamer.spaces.live.com/

********************************************
| Think outside the box! |
********************************************
"dm3281" <dm3281@xxxxxxxxxx> wrote in message news:648C4C38-1D59-41FE-87B6-CB00F3416296@xxxxxxxxxxxxxxxx
Hello --

I need to write an ASP.NET 2.0 application for our clients to use to login and verify file transmissions. Each client will need their own logon, in addition to a way to assign each user a unique customerid. All users beloning to the same custeromid would see the same information on the website.

Can I easily do this using membership services or must I use a combination of membership services and profiles?

For example.

User: jdoe belongs to customerid 1
User: mbrown belongs to customer id 1
User: jlorsong belongs to customer id 2
User: troberts belongs to customer id 3

In this case, when either jdoe or mbrown login, they would see the same information on the website. If jlorsong logs in, he would see only his information.

Thanks


.