views:

2334

answers:

5

I have some tables that have a uniqueidentifier UserID that relates to aspnet_Users.UserID. When the user submits some data for those tables, since the controller method has an [Authorize] I get a User object. I can get the username with User.Identity.Name, but how do I get the UserID to be able to establish (the ownership) relationship?

+1  A: 

Its the ProviderUserKey property.

System.Web.Security.MembershipUser u;
u.ProviderUserKey
Alex
How would I get u to be the current logged in user?
J. Pablo Fernández
+6  A: 

Firstly, this answer is not strictly and MVC answer, but an ASP.NET answer. The fact that your site is MVC is irrelivant to solving the problem, in this case.


Hmm. I'm not very sure how you are handling your users in your system but it sounds like you using the (very evil) asp.net membership provider that comes out of the box with .net. This is hinted by the fact that you said

  • aspnet_Users.UserID
  • UserID is a uniqueidentifier (read: GUID).

With the default forms authentication system, which uses the default FormsIdentity, it only has a single property called Name (as you correctly noted). This means it has only one value where to place some unique user information. In your case, you are putting Name/UserName/DisplayName, in the Name property. I'm assuming this name is their Display Name and it is unique. Whatever value you are putting in here, it HAS TO BE UNIQUE.

From this, you can grab the user's guid.

Check this out.

using System.Web.Security;

....

// NOTE: This is a static method .. which makes things easier to use.
MembershipUser user = Membership.GetUser(User.Identity.Name);
if (user == null)
{
    throw new InvalidOperationException("User [" + 
        User.Identity.Name + " ] not found.");
}

// Do whatever u want with the unique identifier.
Guid guid = (Guid)user.ProviderUserKey;

So, every time you wish to grab the user information, you need to grab it from the database using the static method above.

Read all about the Membership class and MembershipUser class on MSDN.

Bonus Answer / Suggestion

As such, i would CACHE that result so you don't need to keep hitting the database.

... cont from above....
Guid guid = (Guid)user.ProviderUserKey;

Cache.Add(User.Identity.Name, user.UserID); // Key: Username; Value: Guid.

Otherwise, you can create your own Identity class (which inherits from IIdentity) and add you can add your own custom properties, like UserID. Then, whenever you authenticate (and also on every request) you can set this value. Anyway, this is a hard core solution, so go with the caching, right now.

HTH

Pure.Krome
Is that the way to do it? Making the name of the user unique? What do we have IDs for at all then?
J. Pablo Fernández
OT: Why do you claim the ASP.NET Membership is evil?
eduncan911
@Eric: because i personally feel that it's a massively overengineered solution for the majority of scenario's. For example, how many times do u see a solution that shares a common sql server where the users are shared across databases, on that same sql server? All those tables and stored procs, which can be cut down to just one or two for the majority of scenario's people do. Summary: massive bloat. Over enginereed. Side note: OpenID FTW now :)
Pure.Krome
@J. Pablo: no mate. The ID is the main thing that is unique, but the Membership.GetUser(string) gets the user by the string provided -> generally their username. If u don't provide that string, it uses the current value for whoever is logged in, assuming someone IS logged in. That value is the equivalent of User.Identity.Name.
Pure.Krome
+1  A: 

If you are using your own IPrincipal object for authorization, you just need to cast it to access the Id.

For example:

public class MyCustomUser : IPrincipal
{
    public int UserId {get;set;}

    //...Other IPrincipal stuff
}

Here is a great tutorial on creating your own Form based authentication.

http://www.codeproject.com/KB/web-security/AspNetCustomAuth.aspx

That should get you on the right path to creating an authentication cookie for your user and accessing your custom user data.

ebrown
+4  A: 

It seems you cannot get it from the User object but you can get it this way:

Guid userGuid = (Guid)Membership.GetUser().ProviderUserKey;
J. Pablo Fernández
Really? it doesn't require a string? /me checks msdn: http://msdn.microsoft.com/en-us/library/system.web.security.membership.getuser.aspx . Sh|t! u're right! good find :)
Pure.Krome
+3  A: 

If you are using the ASP.NET Membership (which in turn uses the IPrincipal object):

using System.Web.Security;
{
  MembershipUser user = Membership.GetUser(HttpContext.User.Identity.Name);
  Guid guid = (Guid)user.ProviderUserKey;
}

User.Identity always returns the state of the current user, logged in or not.

Anonymous or not, etc. So a check for is logged in:

if (User.Identity.IsAuthenticated)
{
  ...
}

So, putting it all together:

using System.Web.Security;
{
  if (User.Identity.IsAuthenticated)
  {
    MembershipUser user = Membership.GetUser(HttpContext.User.Identity.Name);
    Guid guid = (Guid)user.ProviderUserKey;
  }
}
eduncan911