StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13982193
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-12-20T23:34:08.590
FavoriteCount
0
LastActivityDate
2012-12-20T23:34:08.590
LastEditDate
LastEditorUserId
0
OwnerUserId
80516
ParentId
13870229
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Ultimately went with Yaron's suggestion and wrote a couple custom inspectors & behaviors. Using proxy.ClientCredentials.UserName.UserName/Password was the cause of the original exception reported above. It would try and validate the return SOAP before processing subsequent added behaviors, resulting in response validation errors on the SAML assertion every time. The first behavior/inspector has two jobs: 1) In the request side, manually add UsernameToken nodes; 2) In the response side, extract the saml token; be sure to remove any offending "Security" XML nodes from the SOAP and reprocess the reply (prevents another error like the original post); save the SAML response for later. The second behavior/inspector injects the shared SAML assertion into the remainder of the requests. Here's the config required: <pre><code> <basicHttpBinding> <binding name="Default"> <security mode="Transport"> <transport clientCredentialType="None"/> </security> </binding> </basicHttpBinding> </code></pre> Here's some code (notice the removal of the ClientCredentials behavior): <pre><code>var proxy = new LoginClient(); proxy.ChannelFactory.Endpoint.Behaviors.Remove<ClientCredentials>(); var initLogin = new InitialLoginMessageBehavior("username", "password"); proxy.Endpoint.Behaviors.Add(initLogin); var response = proxy.Login(); //use the SAML response var proxy2 = new OtherClient(); proxy2.ChannelFactory.Endpoint.Behaviors.Remove<ClientCredentials>(); proxy2.Endpoint.Behaviors.Add(new SamlAuthenticationMessageBehavior(initLogin.Saml)); var response2 = proxy2.DoSomethingElse(); </code></pre> Everything you need for creating behaviors and inspectors: <a href="http://msdn.microsoft.com/en-us/library/aa717047(v=vs.100).aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/aa717047(v=vs.100).aspx</a> <a href="http://blogs.msdn.com/b/carlosfigueira/archive/2011/04/19/wcf-extensibility-message-inspectors.aspx" rel="nofollow">http://blogs.msdn.com/b/carlosfigueira/archive/2011/04/19/wcf-extensibility-message-inspectors.aspx</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to process saml:Assertion in WCF?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USwes
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
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.