Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The server returns an x.509 token in the response and WCF is not sure what to do with it (this token is not expected in username auth). I see two options:</p> <ol> <li><p>in your encoder strip out the security tag from the response</p> <p>OR</p></li> <li><p>do not use security at all and in the encoder (or a message inspector if you prefer) push the user/pass headers to the request</p></li> </ol> <p>EDIT: You say this token should be used by the client in further calls. I'm not sure what is the correct way to handle this so I'll give a quick way which will work (but feels a little patchy). Don't define any security at all (remove the security element from the binding). Then use a custom message inspector (or an encoder but it is harder) to push into the message the user/pass in the correct format (see how they are sent when security binding is used). this should not be hard. then WCF will not validate the token on response. you can user the same message inspector you already have in place to inspect the response and extract the token. your main class (which initialize the proxy) is also the class that initialized the inspector so it should have access to its data members in order to access the token and resend it.</p> <p>it would have been so much easier if the server would send you the token inside the body and not header. also there might be a way to do it in a non-patchy weay by implementing custom tokens / behaviors but in my mind this adds more abstraction and it is better to be concrete.</p>
    singulars
    1. This table or related slice is empty.
    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. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

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