Databases
StackOverflow2013
Usersdbo
USLaazik
 

Note that there are some explanatory texts on larger screens.

plurals
  1. USLaazik
    primarykey
    data
    text
    plurals
    1. POHandling REST SWT tokens in WCF WIF pipeline is not working
      singulars
      1. PTQuestion
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COHi, I've been using the sample from here http://code.msdn.microsoft.com/vstudio/Custom-Token-ddce2f55 Now the interesting part then would be that what is the URI that is actually used to compare the token content to the one that the token handler returns. Both the t:TokenType and ValueType would make me think that it is http://schemas.xmlsoap.org/ws/2009/11/swt-token-profile-1.0 , which I'm using. I've been unable to get any token related traces or debugs neither :(
      singulars
      1. POHandling REST SWT tokens in WCF WIF pipeline is not working
      1. USLaazik
    2. COI know, I've been working with ETSI, ITU etc. standards and protocols for last 15 years and they are hard. Nevertheless, statement of "Field must contain value 0xXYZ in network byte order." - has a lot of ambiguity in this sentence. It turns up it is already presented in the RFC in network byte order, I initially took the value and did change the ordering (according to my interpretation), which didn't work. So I still think that it is really hard to interpret this specific chapter and could be done better :).
      singulars
      1. PO
      1. USLaazik
    3. COAlthough I agree, that the RFC 5389 is detailing the STUN in great detail, after I tried to implement the header format, the conclusion at least from me was that it's one of the messiest wordings I have had to deal with. Using binary/hex notations in network/non-network orders in a mix ... It is very hard to follow and understand.
      singulars
      1. PO
      1. USLaazik
 

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