Question

我正试图修改和增加海关头盔,使之达到<代码>的飞跃信息。更正前类似方法:

    public object BeforeSendRequest(ref System.ServiceModel.Channels.Message request, IClientChannel channel)
    {
        MessageHeader header = MessageHeader.CreateHeader("name", "http://myname", "Oscar");
        request.Headers.Add(header);

        return null;
    }

此时此刻,歌手在像头一样的跳板上添加:

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<s:Header>
<ActivityId CorrelationId="51efbfdb-2187-45b9-81fc-6a38815d5bed" xmlns="http://schemas.microsoft.com/2004/09/ServiceModel/Diagnostics">d1351a78-a53a-4d32-ad35-fca6d4262adf</ActivityId>
<name xmlns="http://myname">Oscar</name>
</s:Header>

问题在于,我想在头脑中增加一些大事,最后结果必须如此:

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<s:Header>
<ActivityId CorrelationId="51efbfdb-2187-45b9-81fc-6a38815d5bed" xmlns="http://schemas.microsoft.com/2004/09/ServiceModel/Diagnostics">d1351a78-a53a-4d32-ad35-fca6d4262adf</ActivityId>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
    <wsse:UsernameToken xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
      <wsse:Username xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">username</wsse:Username>
      <wsse:Password xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">password</wsse:Password>
    </wsse:UsernameToken>
</wsse:Security>
</s:Header>

是否有办法实现这一目标?

PS。请辩:-)不要批评我,我的情况如下:

在增加这一用户名和密码时,你需要超过<条码><>>>><>/代码>,问题是,我试图通信的基于 Java的网络服务列在<条码>之下。我认为,由于第3条链接<>,这一服务不符合规定。在无担保关系上通过全权证书被认为是不好的做法。”

我也阅读了这些联系,并尝试了这些联系。另外,在从第1和第2号链接中做事时,我在视频演播室中还有一个例外,如,预计可上网查阅“”。因此,我正在尝试使用<条码>。

Answer 1

第3参数是制造头盔。缺席时,该物体采用数据查询器进行序列化,这样,如果你订立数据合同,显示主机结构的模型,你可以把一个实例作为第三参数,并会创建你想要的头盔。

Answer 2

通告周知解决办法

Answer 3

我有同样的问题,尽管我的服务是https。这应该是一个组合问题,因此,你没有必要手工处理。

Anyway, you don t have to use the MessageInspectors using BeforeSendRequest. You should try and change the config generated code adding some security configuration. WCF will then create what headers you need. Then in code add the credentials and you should be ok.

I imagine that the generated proxy is creating you a customBinding or basicHttpBinding. basicHttpBinding though not supporting the WS-Security specifications, so you should change this either to custom or wsHttpBinding. You can play with and find the correct configuration to gain the desired results.

我补充说,“Sample config syntax”

<customBinding>
        <binding name="MessageServerBinding">
          <security defaultAlgorithmSuite="Default" authenticationMode="UserNameOverTransport"
            requireDerivedKeys="true" includeTimestamp="true" messageSecurityVersion="WSSecurity10WSTrustFebruary2005WSSecureConversationFebruary2005WSSecurityPolicy11BasicSecurityProfile10">
            <secureConversationBootstrap />
          </security>
........
</binding>
</customBinding>

这是一种样本配置,例如,你可能不需要列入一个时间序列,或者如果我记得确实需要一些更高的效率,那么你可能需要一个不了。

为检查这一讨论:WCF: Adding Nonce tousername Token

Hope this helps.

友情链接