Databases
StackOverflow2013
Postsdbo
POHandling different types of users in asp.net mvc
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHandling different types of users in asp.net mvc
    primarykey
    data
    text
    <p>I have 3 different types of users (with different roles) interacting on my web application, they all perform some task - some can be exactly the same e.g. create a quote others can be unique to that specific user e.g. sign off quote.</p> <p>For more clarity 3 types of users: Client, Supplier, Customer.</p> <p>Client or Customer can create a quote, however only the Customer can sign off a quote.</p> <p>How do I ensure my application allows clients to access client speficic controllers and suppliers to access supplier specific controllers or areas. Via Custom Attributes? Do I store the type of user inside a cookie? Is this safe? or Session state? As soon as someone logs onto the system I send back a LoggedOnDTO object on which I store Username, UserID, and type of user....</p> <p>NOTE: I went away from asp.net build in way of creating users, I have my own custom tables with my custom mechanism for logging into the system. I have a registered Model Bindiner that looks for the prefix and I send in a strongly typed object to each action...</p> <p>Sample code:</p> <pre><code>[HttpGet] public ActionResult AddComment(int quoteid, ClientUserDTO loggedonclientuser) { } [HttpGet] public ActionResult AddCommentSupplier(int quoteid, Supplier loggedonsuppluser) { } </code></pre> <p>EDIT: This method for some reason seems so much simpler... Is there something wrong with it? Any possible security issues? Threading?</p> <p>My session controller is:</p> <pre><code>if (_authService.isValidUser(model)) { var data = _authService.GetAuthenticationCookieDetails(model); AuthenticateCookie.AddDetailsToCookie(data); return Redirect(Url.Action("Index", "Activity")); } </code></pre> <p>When I create my cookie... I can simple store "ClientUser", "Supplier" or whatever role they are inside the cookie.</p> <p>Then I can create an Attribute and read in the cookie data to see if they are a valid user e.g.</p> <pre><code>public class ClientAuthorizationAttribute : AuthorizeAttribute { public bool AlwaysAllowLocalRequests = false; protected override bool AuthorizeCore(System.Web.HttpContextBase httpContext) { if (AlwaysAllowLocalRequests &amp;&amp; httpContext.Request.IsLocal) { bool authorized = false; var result = UserDetails.GetTypeFromTicket(httpContext.User.Identity as FormsIdentity); if (result.Equals("client", StringComparison.OrdinalIgnoreCase)) { authorized = true; } //throw no access exception? return authorized; } return base.AuthorizeCore(httpContext); } } </code></pre> <p>Register the attribute under my base controller and I have a simple working solution???</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USHaroon
    1. USHaroon
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHandling different types of users in asp.net mvc
      1. USJoshua
      1. VTFavorite
    2. VO
      singulars
      1. POHandling different types of users in asp.net mvc
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload