StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12030785
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-08-19T23:25:55.100
FavoriteCount
0
LastActivityDate
2012-08-23T15:46:08.307
LastEditDate
2012-08-23T15:46:08.307
LastEditorUserId
270591
OwnerUserId
270591
ParentId
12028604
PostTypeId
2
Score
74
ViewCount
0
LastEditorDisplayName
text
Body
The problem of losing the principal on a new thread is mentioned here: <a href="http://leastprivilege.com/2012/06/25/important-setting-the-client-principal-in-asp-net-web-api/">http://leastprivilege.com/2012/06/25/important-setting-the-client-principal-in-asp-net-web-api/</a> <blockquote> Important: Setting the Client Principal in ASP.NET Web API Due to some unfortunate mechanisms buried deep in ASP.NET, setting Thread.CurrentPrincipal in Web API web hosting is not enough. When hosting in ASP.NET, Thread.CurrentPrincipal might get overridden with HttpContext.Current.User when creating new threads. This means you have to set the principal on both the thread and the HTTP context. </blockquote> And here: <a href="http://aspnetwebstack.codeplex.com/workitem/264">http://aspnetwebstack.codeplex.com/workitem/264</a> <blockquote> Today, you will need to set both of the following for user principal if you use a custom message handler to perform authentication in the web hosted scenario. <pre><code>IPrincipal principal = new GenericPrincipal( new GenericIdentity("myuser"), new string[] { "myrole" }); Thread.CurrentPrincipal = principal; HttpContext.Current.User = principal; </code></pre> </blockquote> I have added the last line <code>HttpContext.Current.User = principal</code> (needs <code>using System.Web;</code>) to the message handler and the <code>User</code> property in the <code>ApiController</code> does always have the correct principal now, even if the thread has changed due to the task in the MediaTypeFormatter. Edit Just to emphasize it: Setting the current user's principal of the <code>HttpContext</code> is only necessary when the WebApi is hosted in ASP.NET/IIS. For self-hosting it is not necessary (and not possible because <code>HttpContext</code> is an ASP.NET construct and doesn't exist when self hosted).
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow can I safely set the user principal in a custom WebAPI HttpMessageHandler?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USSlauma
UserOwnerUserId
1. USSlauma
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow can I safely set the user principal in a custom WebAPI HttpMessageHandler?
 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
 VTUpMod
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.