StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14778633
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-02-08T18:02:28.623
FavoriteCount
0
LastActivityDate
2013-02-08T21:08:02.647
LastEditDate
2013-02-08T21:08:02.647
LastEditorUserId
138062
OwnerUserId
138062
ParentId
13051318
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Thanks spamguy. I figured out a hack to work around the issue and am posting it here for others that may encounter the same problem with the limitations of PowerSchool's OpenID provider. You need to build the request normally with DotNetOpenAuth, then extract the redirect response from the request. Once you have this, you can pull the Location header and overwrite the namespace values as needed. This example is for an MVC application. If you need to do this in a WebForms app, simply take the logic from the method and replace the line <code>return redirectResponse.AsActionResult();</code> with <code>redirectResponse.Send()</code>. You will need to wrap this in the usual try...catch... for ThreadAbortExceptions. namespaces used: <pre><code>using System; using System.Linq; using System.Net; using System.Net.Http; using System.Web.Mvc; using System.Web.Security; using DotNetOpenAuth.Messaging; using DotNetOpenAuth.OpenId; using DotNetOpenAuth.OpenId.Extensions.AttributeExchange; using DotNetOpenAuth.OpenId.RelyingParty; </code></pre> hack: <pre><code>const string NS_DCID = "http://powerschool.com/entity/id"; const string NS_USERTYPE = "http://powerschool.com/entity/type"; static readonly OpenIdRelyingParty openid = new OpenIdRelyingParty(); private ActionResult SubmitOpenIdRequest(string openid_identifier) { var request = openid.CreateRequest(openid_identifier); var ax = new FetchRequest(); // any modification to the following attributes will require a corresponding change in the string replacement hack ax.Attributes.AddRequired(NS_DCID); ax.Attributes.AddRequired(NS_USERTYPE); request.AddExtension(ax); var redirectResponse = request.RedirectingResponse; // PowerSchool is violating the attribute exchange specification, requiring specific namespaces and elements to function // Need to overwrite the values generated by OpenID to patch PowerSchool's incorrect provider implementation redirectResponse.Headers["Location"] = redirectResponse.Headers["Location"] .Replace("openid.ns.alias3", "openid.ns.ax") .Replace("openid.alias3.required=dcid%2Calias2", "openid.ax.required=dcid%2Cusertype") .Replace("openid.alias3.mode", "openid.ax.mode") .Replace("openid.alias3.type.alias1", "openid.ax.type.dcid") .Replace("openid.alias3.count.alias1", "openid.ax.count.dcid") .Replace("openid.alias3.type.alias2", "openid.ax.type.usertype") .Replace("openid.alias3.count.alias2", "openid.ax.count.usertype"); return redirectResponse.AsActionResult(); } </code></pre> Be warned: this is a fragile hack. Internal changes in DNOA or changes to the FetchRequest can break the replacement logic.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POForcing a different Attribute Exchange namespace in DotNetOpenAuth
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USBrandon
UserOwnerUserId
1. USBrandon
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POForcing a different Attribute Exchange namespace in DotNetOpenAuth
 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
 VTAcceptedByOriginator
2. 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.