CODEWITHSUNDEEP
asp.netrolesuser-management
TheTechGuy
TheTechGuy

Reputation: 17384

"Role Management" vs "User Management" in ASP.NET

Question No 1

I am familiar with role management, a particular member in a particular role can do this and access this functionally. What I need to do is Manage individual user, not the role he is in.

For example, lets say I create a role, called "Sales". I setup the role permission what the sales persons can do. Now i want to keep a check on individual user. For example if this is "john", i want to show him the records only he created. If his is peter, I want to show him only that records which he created, not by john or other sales people.

Is there a thing called "User Management" in ASP.NET that we can use? If not we have to create it ourselves and I believe the integration with ASP.NET "Role Management" will not be that smooth.

Question No 2.

I am using control for user login. I want to create a session at this time so I can keep track of which user is signed in so I can show him the records only pertaining to him. How can I do that?

Upvotes: 0

Views: 1276

Answers (4)

pseudocoder
pseudocoder

Reputation: 4402

1) If you want to filter records by the creating user, you need to record in your table the ID of the user who created the record. You can access the name of current user through User.Identity.Name and their ID (provider-dependent) through User.ProviderUserKey.

2) Sessions are created automatically in ASP.NET and provided you have a properly configured MembershipProvider, you can retrieve all the needed user info using the User object as shown above.

It sounds like you are a little unfamiliar with ASP.NET Membership and Roles capabilities, because they are actually set up quite well to accomplish what you are describing. I would recommend checking out this tutorial series:

https://web.archive.org/web/20211020202857/http://www.4guysfromrolla.com/articles/120705-1.aspx

Upvotes: 0

Bueller
Bueller

Reputation: 2344

You are talking about Authentication and Authorization. For question 1 you and implement a custom authorization provider to allow for user level control http://msdn.microsoft.com/en-us/library/aa479048.aspx For question 2, once you log in and are Authenticated, the session contains a userprinciple object that has the info in it automatically.

Upvotes: 0

David
David

Reputation: 73594

See ASP.NET Profile Properties.

Assuming the records in the database correspond to a unique ID for a user, you can store the unique id in a profile property per user.

Upvotes: 1

The Evil Greebo
The Evil Greebo

Reputation: 7138

Your Q1 isn't really about Role vs User management (ie: authorizations) at this point. It's about audit tracking within your application.

And the way you do that is you capture the ID of the user who created the record in question with the record, so that later you can filter on that ID.

Pseudo database structure

Table Sales
    Field...
    Field...
    Field...
    CreatedByUser int not null, -- Populate this on creation and never change it again
    ModifiedByUser int not null - populate this on every row update including insert

Upvotes: 1

Related Questions