StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3067717
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-06-18T06:55:13.863
FavoriteCount
0
LastActivityDate
2010-06-18T06:55:13.863
LastEditDate
LastEditorUserId
0
OwnerUserId
38087
ParentId
3065288
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
With MVC it is simple to bypass the Membership and Role provider framework altogether. Sometimes it is easier to do this than to implement custom Membership/Role providers, in particular if your authn/authz model doesn't quite fit the mold of those providers. First, you should realize that you don't need to write everything from scratch, you can use the core Forms authentication API, which can be used independently of the Membership/Role provider framework: <ul> <li><code>FormsAuthentication.SetAuthCookie</code> - Call this after user has been authenticated, specify the user name</li> <li><code>Request.IsAuthenticated</code> - Returns true if SetAuthCookie was called</li> <li><code>HttpContext.Current.User.Identity.Name</code> - Returns the user name specified in the call to SetAuthCookie</li> </ul> So here is what you do in MVC to bypass the Membership/Role provider: <ol> <li>Authentication: In your controller, authenticate the user using your custom logic.If successful, call <code>FormsAuthentication.SetAuthCookie</code> with the user name.</li> <li>Authorization: Create a custom authorize attribute (deriving from AuthorizeAttribute) . In the <code>AuthorizeCore</code> override, implement your custom authorization logic, taking the user in <code>HttpContext.Current.User.Identity.Name</code> and the roles defined in the Roles property of the AuthorizeAttribute base class. Note you can also define properties on your custom authorization attribute and use that in your authorization logic. For example you can define a property representing roles as enumerated values specific to your app, instead of using the Roles property which is just a string.</li> <li>Affix your controllers and actions with your custom authorize attribute, instead of the default Authorize attribute.</li> </ol>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POASP.NET MVC2 and MemberShipProvider: How well do they go together?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USDSO
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POASP.NET MVC2 and MemberShipProvider: How well do they go together?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
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.