By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,180 Members | 1,051 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,180 IT Pros & Developers. It's quick & easy.

Membership Services and Client Logins?

P: n/a
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

Jun 27 '08 #1
Share this Question
Share on Google+
3 Replies


P: n/a
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" <dm****@nospam.netwrote in message
news:64**********************************@microsof t.com...
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
Jun 27 '08 #2

P: n/a
Wait a minute. Where could custom providers be implied by the question and
given example? Not needed IMO.

Sure roles --are-- useful here. As I read it the presumed context of some
customerid functions as some role users can be assigned to. And only then
due to the lack of also knowing how the page and sections of the page itself
can be configured with templates to enable or disable display or access to
content and controls on the page based on a role a member has been assigned
to; silver, gold and platinum for example to use some cheesy examples.

The Profile Table provider released after everybody realized how FUBAR
Profiles were implemented once 2.0 was released is much better storing
properties and other meta data for each user; street address, telephone
numbers and so on --but-- while the Table Provider is a big improvement it
does not support the relational model or normalization.

Given what we were told I think Membership and Roles will be just fine
without the need for custom providers.


"Cowboy (Gregory A. Beamer)" <No************@comcast.netNoSpamMwrote in
message news:eF**************@TK2MSFTNGP03.phx.gbl...
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" <dm****@nospam.netwrote in message
news:64**********************************@microsof t.com...
>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
Jun 27 '08 #3

P: n/a
Thanks for the post.

I was thinking I would just need to create a role for each client that I
have. i.e, "Cust100", "Cust101", "Cust102", "Custom103", etc.

After users have registered, I could then go in and assign what role they
belong to.

I was thinking once they login, the page can then use GetRolesForUser()
method to return the role they belong to. Since I need to the whether they
are Customer 100, 101, 102, etc., I could get their number and use this as
the ID into my own tables when I need to query for their data.

Does this make sense???

I know this may not be how Membership provider is typically used -- since I
don'e have clearly defined roles for one person like Admin, Developer, User,
Publisher, etc., and I'm not trying to restrict specific web pages from
displaying... I'm mainly trying to determine what Customer # they are so I
can display a gridview with only their data.


"clintonG" <no****@nowhere.comwrote in message
news:O1**************@TK2MSFTNGP05.phx.gbl...
Wait a minute. Where could custom providers be implied by the question and
given example? Not needed IMO.

Sure roles --are-- useful here. As I read it the presumed context of some
customerid functions as some role users can be assigned to. And only then
due to the lack of also knowing how the page and sections of the page
itself can be configured with templates to enable or disable display or
access to content and controls on the page based on a role a member has
been assigned to; silver, gold and platinum for example to use some cheesy
examples.

The Profile Table provider released after everybody realized how FUBAR
Profiles were implemented once 2.0 was released is much better storing
properties and other meta data for each user; street address, telephone
numbers and so on --but-- while the Table Provider is a big improvement it
does not support the relational model or normalization.

Given what we were told I think Membership and Roles will be just fine
without the need for custom providers.


"Cowboy (Gregory A. Beamer)" <No************@comcast.netNoSpamMwrote in
message news:eF**************@TK2MSFTNGP03.phx.gbl...
>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" <dm****@nospam.netwrote in message
news:64**********************************@microso ft.com...
>>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
Jun 27 '08 #4

This discussion thread is closed

Replies have been disabled for this discussion.