Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>Question #1:</strong></p> <blockquote> <p>I need my AX requests to be in the namespace openid.ax, not openid.alias3. How do I force DotNetOpenAuth to do that?</p> </blockquote> <p>DotNetOpenAuth doesn't let you force the alias of a specific extension. To require a specific one is contrary to the OpenID 2.0 specification. Even the <a href="http://openid.net/specs/openid-attribute-exchange-1_0.html#anchor2" rel="nofollow">AX extension itself states this in section 1.1</a></p> <blockquote> <blockquote> <p><code>openid.ns.&lt;extension_alias&gt;=http://openid.net/srv/ax/1.0</code></p> </blockquote> <p>The actual extension namespace alias should be determined on a per-message basis by the party composing the messages, in such a manner as to avoid conflicts between multiple extensions. For the purposes of this document, the extension namespace alias for the attribute exchange service will be "ax". </p> </blockquote> <p><strong>Question #2:</strong></p> <blockquote> <p>The API requires requested properties be named just so -- in this case, 'student-ids'. Above, they're getting default names like 'alias1'. How do I force DotNetOpenAuth to label properties with custom names?</p> </blockquote> <p>Just like for your first question, DotNetOpenAuth doesn't provide a way for you to coerce aliases of individual attributes because the AX extension doesn't allow for those types of requirements. The type of the attribute is given in the URI. The alias of that attribute is definable by the relying party and the OpenID Provider is supposed to look at the Type URI of the attribute, and accept whatever alias comes from the relying party.</p> <p><strong>Question #3:</strong></p> <blockquote> <p>Who's in the right here: the API for requiring openid.ax or DotNetOpenAuth for not caring?</p> </blockquote> <p>DotNetOpenAuth is correct. If indeed the alias differences between the documentation you're looking at for this student-id exchange and what DotNetOpenAuth are the root cause of the problem you're seeing with the AX attributes being ignored, then the fault lies with a poor implementation of an OpenID Provider being run at the server. Poor implementations of OpenID Providers are very scary -- not just for poor interop, but because they suggest there may be any of many possible security issues as well given the lack of care in implementing the spec properly.</p> <p>I suggest you try using Fiddler or some other HTTP sniffer to intercept an outbound request, fix up all the aliases to match what the docs suggest they should be, and see if it fixes the problem. If so, the OpenID Provider should be fixed and you can contact them to request they upgrade to a newer version of whatever library they're using (hopefully that alone will fix it). If "fixing" the aliases does <em>not</em> fix the problem, then you can move along to investigating other possible reasons for the interop failure.</p>
    singulars
    1. This table or related slice is empty.
    1. POForcing a different Attribute Exchange namespace in DotNetOpenAuth
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USAndrew Arnott
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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. VTUpMod
    1. COFollowup: using Fiddler to try the ax namespace was a good idea. It ultimately proved that the provider is expecting a) AX requests in .ax and b) explicitly named attributes. They fessed up and said a fix is coming...eventually. Until then I'm not sure what I'll do...
      singulars
      1. PO
      1. USspamguy
    2. CO+1 Thanks Andrew. It would have been a long road to find the workaround without your answer.
      singulars
      1. PO
      1. USBrandon
    3. COIndeed. I would accept both Brandon's and your answers if I could.
      singulars
      1. PO
      1. USspamguy
 

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