Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I can think of alternative ways to implement this, but they all involve using a customized AuthorizeAttribute. One way to do this would be to have a base controller using said customized AuthorizeAttribute that all of your controllers derive from. This attribute would be customized to prevent anonymous (and unauthorized) access to an action unless it's controller or the action itself has been decorated with another attribute -- say the AnonymousEnabledAttribute. All of your controllers would derive from this controller and thus inherit it's standard "no anonymous by default" behavior. You would then simply decorate the controllers/actions you want to be anonymous with the AnonymousEnabledAttribute -- providing the override for that controller or action. Or, for a controller, simply don't inherit from the protected controller and all of it's actions become public.</p> <p>Oh, and your whole site would have to remain open.</p> <pre><code>[OverridableAuthorize] public abstract class ProtectedController : Controller { } public class MostlyProtectedController : ProtectedController { public ActionResult ProtectedAction() { } [AnonymousEnabled] public ActionResult PublicAction() { } } [AnonymousEnabled] public class ExplicitlyPublicController : ProtectedController { // inherits additional behaviors, but anonymous is enabled by attribute } public class PublicByOmissionController : Controller { // doesn't inherit and is thus public -- assuming whole site is open } public class AnonymousEnabledAttribute : Attribute { } public class OverridableAuthorizeAttribute : AuthorizeAttribute { public override void OnAuthorization( AuthorizationContext context ) { context.HttpContext.Items["ActionDescriptor"] = context.ActionDescriptor; base.OnAuthorize( context ); } public override bool AuthorizeCore( HttpContextBase context ) { var actionDescriptor = context.Items["ActionDescriptor"] as ActionDescriptor; if (actionDescriptor == null) { throw InvalidOperationException( "ActionDescriptor missing from context" ); } var attribute = actionDescriptor .GetCustomAttributes( typeof(AnonymousEnabledAttribute,true) .FirstOrDefault(); if (attribute == null) { return base.AuthorizeCore( context ); } return true; } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POASP.NET MVC 2 authorization problem
      singulars
      1. PTQuestion
    1. PTAnswer
    1. UStvanfosson
    1. UStvanfosson
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POASP.NET MVC 2 authorization problem
      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
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for this suggestion. So, this would mean the site (as per the web.config) would be totally open but all controllers would be locked down by default so as long as they inherit from the ProtectedController?
      singulars
      1. PO
      1. UScbmeeks
    2. CO@cbmeeks - correct. Also, I think using the AuthorizeAttribute (or something derived from it), i.e, MVC security, is definitely preferable to trying to mix WebForms-based security and MVC security.
      singulars
      1. PO
      1. UStvanfosson
    3. CO** CAUTION ** The AuthorizeAttribute class must be immutable once it is created. You can use HttpContext.Items to store the ActionDescriptor, but you absolutely *MUST NOT* store it as an instance field inside the class. The reason for this is that a single instance of AuthorizeAttribute can be used to process multiple concurrent requests, and by introducing an instance field you now have a race condition in your security code.
      singulars
      1. PO
      1. USLevi
 

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