Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This is not a problem. You have a variety of options available to you. One approach is to blend Forms Authentication with your own security model.</p> <p>The basic idea is to let Forms Auth create and manage a ticket (in the form of an encrypted ticket) for the logged-in user. The ticket is used to determine whether or not someone is logged in, and who they are. You can then mix in any additional security related logic on top of that.</p> <p>To process the login request, you just have a controller and action like you normally would. Note: in the example below, I am making some assumptions about <code>LoginViewModel</code>, the service you are using to authenticate, and the object it returns if any. You'll have to sub in your actual logic.</p> <pre><code>public ActionResult Login(LoginViewModel model) { // make sure the user filled out the login fields correctly if (!ModelState.IsValid) return View(model); // authenticate the user here var authenticatedUser = AuthorizeUserUsingRemoteWebService(model.Username, model.Password); if (authenticatedUser.IsAuthenticated) { // create forms auth ticket cookie and redirect to the home page FormsAuthentication.SetAuthCookie(authenticatedUser.Username); return RedirectToAction("Index", "Home"); } // authentication failed, so show the login page again return View(model); } </code></pre> <p>In addition to that, you may have an HTTP module that handles the AuthenticateRequest event. Your module will be registered after the Forms Auth HTTP module, so it will have already processed whether or not the user is logged in. What you want to do is look up additional information if they are logged in, to get roles and such.</p> <pre><code>public class CustomAuthHttpModule : IHttpModule { public void Init(HttpApplication context) { context.AuthenticateRequest += new EventHandler(OnAuthenticateRequest); } void OnAuthenticateRequest(object sender, EventArgs e) { HttpApplication application = (HttpApplication)sender; HttpContext context = appObject.Context; // user isn't logged in, so don't do anything else if (!context.User.Identity.IsAuthenticated) return; // look up the roles for the specified user, returning the role names as an array of strings string[] roles = LookupUserRolesFromWebService(context.User.Identity.Name); // replace the current User principal with a new one that includes the roles we discovered for that user. context.User = new GenericPrincipal(new GenericIdentity(context.User.Identity.Name), roles); } } </code></pre> <p>You'll register the HTTP module in your web.config:</p> <pre><code>&lt;httpModules&gt; &lt;add name="CustomAuthHttpModule" type="MyAssembly.CustomAuthenticationModule, MyAssembly" /&gt; &lt;/httpModules&gt; </code></pre> <p>You can now use the User object in your MVC controllers and views, the <code>AuthenticatedAttribute</code>, etc.</p> <p>However, I'd recommend that you cache the results of looking up a user's roles so you don't hammer your web service. I'll leave that up to you.</p>
    singulars
    1. This table or related slice is empty.
    1. POusing asp.net authentication with custom authentication
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USHackedByChinese
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POusing asp.net authentication with custom authentication
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    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