blocks|key|119176|text|假设您的web.config中有名为localhost的服务引用，则可以执行以下操作|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|119177|localhost.Service+objWebService+=+newlocalhost.Service();
localhost.AuthSoapHd+objAuthSoapHeader+=+newlocalhost.AuthSoapHd();
string+strUsrName+=ConfigurationManager.AppSettings["UserName"];
string+strPassword+=ConfigurationManager.AppSettings["Password"];

objAuthSoapHeader.strUserName+=+strUsrName;
objAuthSoapHeader.strPassword+=+strPassword;

objWebService.AuthSoapHdValue+=objAuthSoapHeader;
string+str+=+objWebService.HelloWorld();

Response.Write(str);|code-block|syntax|javascript|119178|entityMap^0|4|A|I|9|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|L|$]]

Suppose you have service reference of the name <code>localhost</code> in your <code>web.config</code> so you can go as follows

<pre><code>localhost.Service objWebService = newlocalhost.Service();
localhost.AuthSoapHd objAuthSoapHeader = newlocalhost.AuthSoapHd();
string strUsrName =ConfigurationManager.AppSettings["UserName"];
string strPassword =ConfigurationManager.AppSettings["Password"];

objAuthSoapHeader.strUserName = strUsrName;
objAuthSoapHeader.strPassword = strPassword;

objWebService.AuthSoapHdValue =objAuthSoapHeader;
string str = objWebService.HelloWorld();

Response.Write(str);
</code></pre>

blocks|key|119214|text|可能有一种更聪明的方法，但您可以像这样手动添加标头：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|119215|var+client+=+new+IdentityProofingService.IdentityProofingWSClient();

using+(new+OperationContextScope(client.InnerChannel))
{
++++OperationContext.Current.OutgoingMessageHeaders.Add(
++++++++new+SecurityHeader("UsernameToken-49",+"12345/userID",+"password123"));
++++client.invokeIdentityService(new+IdentityProofingRequest());
}|code-block|syntax|javascript|119216|这里，SecurityHeader是一个自定义实现的类，它需要一些其他类，因为我选择使用属性来配置XML序列化：|offset|length|style|CODE|119217|public+class+SecurityHeader+:+MessageHeader
{
++++private+readonly+UsernameToken+_usernameToken;

++++public+SecurityHeader(string+id,+string+username,+string+password)
++++{
++++++++_usernameToken+=+new+UsernameToken(id,+username,+password);
++++}

++++public+override+string+Name
++++{
++++++++get+{+return+"Security";+}
++++}

++++public+override+string+Namespace
++++{
++++++++get+{+return+"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";+}
++++}

++++protected+override+void+OnWriteHeaderContents(XmlDictionaryWriter+writer,+MessageVersion+messageVersion)
++++{
++++++++XmlSerializer+serializer+=+new+XmlSerializer(typeof(UsernameToken));
++++++++serializer.Serialize(writer,+_usernameToken);
++++}
}


[XmlRoot(Namespace+=+"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd")]
public+class+UsernameToken
{
++++public+UsernameToken()
++++{
++++}

++++public+UsernameToken(string+id,+string+username,+string+password)
++++{
++++++++Id+=+id;
++++++++Username+=+username;
++++++++Password+=+new+Password()+{Value+=+password};
++++}

++++[XmlAttribute(Namespace+=+"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd")]
++++public+string+Id+{+get;+set;+}

++++[XmlElement]
++++public+string+Username+{+get;+set;+}

++++[XmlElement]
++++public+Password+Password+{+get;+set;+}
}

public+class+Password
{
++++public+Password()
++++{
++++++++Type+=+"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText";
++++}

++++[XmlAttribute]
++++public+string+Type+{+get;+set;+}

++++[XmlText]
++++public+string+Value+{+get;+set;+}
}|119218|我没有向UsernameToken+XML添加Nonce位，但它与Password非常相似。还需要添加Created元素，但它是一个简单的[XmlElement]。|119219|entityMap^0|0|0|3|E|0|0|4|D|N|5|X|8|1F|7|1X|C|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@$I|V|J|W|K|L]]|9|@]|A|$]]|$1|M|3|N|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|Y|8|@$I|Z|J|10|K|L]|$I|11|J|12|K|L]|$I|13|J|14|K|L]|$I|15|J|16|K|L]|$I|17|J|18|K|L]]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|R|$]]

There is probably a smarter way, but you can add the headers manually like this:

<pre><code>var client = new IdentityProofingService.IdentityProofingWSClient();

using (new OperationContextScope(client.InnerChannel))
{
 OperationContext.Current.OutgoingMessageHeaders.Add(
 new SecurityHeader("UsernameToken-49", "12345/userID", "password123"));
 client.invokeIdentityService(new IdentityProofingRequest());
}
</code></pre>

Here, <code>SecurityHeader</code> is a custom implemented class, which needs a few other classes since I chose to use attributes to configure the XML serialization:

<pre><code>public class SecurityHeader : MessageHeader
{
 private readonly UsernameToken _usernameToken;

 public SecurityHeader(string id, string username, string password)
 {
 _usernameToken = new UsernameToken(id, username, password);
 }

 public override string Name
 {
 get { return "Security"; }
 }

 public override string Namespace
 {
 get { return "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"; }
 }

 protected override void OnWriteHeaderContents(XmlDictionaryWriter writer, MessageVersion messageVersion)
 {
 XmlSerializer serializer = new XmlSerializer(typeof(UsernameToken));
 serializer.Serialize(writer, _usernameToken);
 }
}


[XmlRoot(Namespace = "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd")]
public class UsernameToken
{
 public UsernameToken()
 {
 }

 public UsernameToken(string id, string username, string password)
 {
 Id = id;
 Username = username;
 Password = new Password() {Value = password};
 }

 [XmlAttribute(Namespace = "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd")]
 public string Id { get; set; }

 [XmlElement]
 public string Username { get; set; }

 [XmlElement]
 public Password Password { get; set; }
}

public class Password
{
 public Password()
 {
 Type = "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText";
 }

 [XmlAttribute]
 public string Type { get; set; }

 [XmlText]
 public string Value { get; set; }
}
</code></pre>

I have not added the <code>Nonce</code> bit to the <code>UsernameToken</code> XML, but it is very similar to the <code>Password</code> one. The <code>Created</code> element also needs to be added still, but it's a simple <code>[XmlElement]</code>.

blocks|key|336739|text|上面的答案大错特错！请勿添加自定义标头。从您的示例xml判断，它是一个标准的WS-Security标头。WCF绝对支持它的开箱即用。在添加服务引用时，应该在配置文件中为您创建basicHttpBinding绑定。您必须对其进行修改，以包含模式为TransportWithMessageCredential的安全元素和clientCredentialType+=UserName的消息元素：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|336740|<basicHttpBinding>
++<binding+name="usernameHttps">
++++<security+mode="TransportWithMessageCredential">
++++++<message+clientCredentialType="UserName"/>
++++</security>
++</binding>
</basicHttpBinding>|code-block|syntax|javascript|336741|上面的配置告诉WCF在HTTPS上的SOAP头中需要userid/password。然后，您可以在进行调用之前在代码中设置id/password：|336742|var+service+=+new+MyServiceClient();
service.ClientCredentials.UserName.UserName+=+"username";
service.ClientCredentials.UserName.Password+=+"password";|336743|除非这个特定的服务提供商偏离了标准，否则它应该是有效的。|336744|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

The answers above are so wrong! DO NOT add custom headers. Judging from your sample xml, it is a standard WS-Security header. WCF definitely supports it out of the box. When you add a service reference you should have basicHttpBinding binding created for you in the config file. You will have to modify it to include security element with mode TransportWithMessageCredential and message element with clientCredentialType = UserName:

<pre class="lang-xml prettyprint-override"><code>&lt;basicHttpBinding&gt;
 &lt;binding name="usernameHttps"&gt;
 &lt;security mode="TransportWithMessageCredential"&gt;
 &lt;message clientCredentialType="UserName"/&gt;
 &lt;/security&gt;
 &lt;/binding&gt;
&lt;/basicHttpBinding&gt;
</code></pre>

The config above is telling WCF to expect userid/password in the SOAP header over HTTPS. Then you can set id/password in your code before making a call:

<pre><code>var service = new MyServiceClient();
service.ClientCredentials.UserName.UserName = "username";
service.ClientCredentials.UserName.Password = "password";
</code></pre>

Unless this particular service provider deviated from the standard, it should work.

blocks|key|119296|text|添加一个自定义的硬编码头可能会起作用(有时也可能会被拒绝)，但这是完全错误的方法。WSSE的目的是安全性。正是由于这个原因，微软发布了Microsoft+Web+Services+Enhancements+2.0，随后又发布了WSE+3.0。您需要安装此软件包(http://www.microsoft.com/en-us/download/details.aspx?id=14089)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|119297|文档并不容易理解，特别是对于那些没有使用过SOAP和WS-Addressing的人。首先，"BasicHttpBinding“是SOAP1.1，它不会为您提供与WSHttpBinding相同的消息头。安装该程序包并查看示例。您需要引用WSE+3.0中的DLL，并且还需要正确设置您的消息。WS+Addressing+header上有大量的数据或变体。您要查找的是UsernameToken配置。|119298|这是一个较长的解释，我应该为每个人写一些东西，因为我在任何地方都找不到正确的答案。您至少需要从WSE+3.0包开始。|119299|entityMap|0|LINK|mutability|MUTABLE|url|http://www.microsoft.com/en-us/download/details.aspx?id=14089^0|3N|1P|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

Adding a custom hard-coded header may work (it also may get rejected at times) but it is totally the wrong way to do it. The purpose of the WSSE is security. Microsoft released the Microsoft Web Services Enhancements 2.0 and subsequently the WSE 3.0 for this exact reason. You need to install this package (<a href="http://www.microsoft.com/en-us/download/details.aspx?id=14089" rel="nofollow">http://www.microsoft.com/en-us/download/details.aspx?id=14089</a>). 

The documentation is not easy to understand, especially for those who have not worked with SOAP and the WS-Addressing. First of all the "BasicHttpBinding" is Soap 1.1 and it will not give you the same message header as the WSHttpBinding. Install the package and look at the examples. You will need to reference the DLL from WSE 3.0 and you will also need to setup your message correctly. There are a huge number or variations on the WS Addressing header. The one you are looking for is the UsernameToken configuration. 

This is a longer explanation and I should write something up for everyone since I cannot find the right answer anywhere. At a minimum you need to start with the WSE 3.0 package.

blocks|key|119327|text|假设您正在使用HttpWebRequest和HttpWebResponse调用web服务，因为.Net客户端确实支持您尝试使用的WSLD的结构。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|119328|在这种情况下，您可以在标头上添加安全凭据，如下所示：|119329|<soap:Envelpe>
<soap:Header>
++++<wsse:Security+soap:mustUnderstand='true'+xmlns:wsse='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd'+xmlns:wsu='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd'><wsse:UsernameToken+wsu:Id='UsernameToken-3DAJDJSKJDHFJASDKJFKJ234JL2K3H2K3J42'><wsse:Username>YOU_USERNAME/wsse:Username><wsse:Password+Type='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText'>YOU_PASSWORD</wsse:Password><wsse:Nonce+EncodingType='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary'>3WSOKcKKm0jdi3943ts1AQ==</wsse:Nonce><wsu:Created>2015-01-12T16:46:58.386Z</wsu:Created></wsse:UsernameToken></wsse:Security>
</soapHeather>
<soap:Body>
</soap:Body>


</soap:Envelope>|code-block|syntax|javascript|119330|您可以使用SOAPUI通过http日志获取wsse+Security。|119331|要小心，因为这不是一个安全的场景。|119332|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Suppose you are calling a web service using HttpWebRequest and HttpWebResponse, because .Net client doest support the structure of the WSLD that your are trying to consume.

In that case you can add the security credentials on the headers like:

<pre><code>&lt;soap:Envelpe&gt;
&lt;soap:Header&gt;
 &lt;wsse:Security soap:mustUnderstand='true' xmlns:wsse='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd' xmlns:wsu='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd'&gt;&lt;wsse:UsernameToken wsu:Id='UsernameToken-3DAJDJSKJDHFJASDKJFKJ234JL2K3H2K3J42'&gt;&lt;wsse:Username&gt;YOU_USERNAME/wsse:Username&gt;&lt;wsse:Password Type='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText'&gt;YOU_PASSWORD&lt;/wsse:Password&gt;&lt;wsse:Nonce EncodingType='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary'&gt;3WSOKcKKm0jdi3943ts1AQ==&lt;/wsse:Nonce&gt;&lt;wsu:Created&gt;2015-01-12T16:46:58.386Z&lt;/wsu:Created&gt;&lt;/wsse:UsernameToken&gt;&lt;/wsse:Security&gt;
&lt;/soapHeather&gt;
&lt;soap:Body&gt;
&lt;/soap:Body&gt;


&lt;/soap:Envelope&gt;
</code></pre>

You can use SOAPUI to get the wsse Security, using the http log.

Be careful because it is not a safe scenario.

blocks|key|119380|text|显然，这篇文章已经存在了几年了--但事实是，我在寻找类似的问题时确实找到了它。在我们的示例中，我们必须将用户名/密码信息添加到Security头中。这与在Security标头之外添加标头信息不同。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|119381|执行此操作的正确方法(对于自定义绑定/+authenticationMode="CertificateOverTransport")+(如.Net框架版本4.6.1)+)是像往常一样添加客户端凭据：|119382|++++client.ClientCredentials.UserName.UserName+=+"[username]";
++++client.ClientCredentials.UserName.Password+=+"[password]";|code-block|syntax|javascript|119383|然后在安全绑定元素中添加一个"token“-因为当身份验证模式设置为证书时，用户名/+pwd凭证在默认情况下不会包括在内。|119384|您可以像这样设置此内标识：|119385|++++//Get+the+current+binding+
++++System.ServiceModel.Channels.Binding+binding+=+client.Endpoint.Binding;
++++//Get+the+binding+elements+
++++BindingElementCollection+elements+=+binding.CreateBindingElements();
++++//Locate+the+Security+binding+element
++++SecurityBindingElement+security+=+elements.Find<SecurityBindingElement>();

++++//This+should+not+be+null+-+as+we+are+using+Certificate+authentication+anyway
++++if+(security+!=+null)
++++{
++++UserNameSecurityTokenParameters+uTokenParams+=+new+UserNameSecurityTokenParameters();
++++uTokenParams.InclusionMode+=+SecurityTokenInclusionMode.AlwaysToRecipient;
security.EndpointSupportingTokenParameters.SignedEncrypted.Add(uTokenParams);
++++}

+++client.Endpoint.Binding+=+new+CustomBinding(elements.ToArray());|119386|这应该就行了。如果没有上面的代码(显式添加用户名令牌)，即使在客户端凭据中设置用户名信息也可能不会将这些凭据传递给服务。|119387|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|V|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|F|7|X|8|@]|9|@]|A|$G|H]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

Obviously it has been some years this post has been alive - but the fact is I did find it when looking for a similar issue. In our case, we had to add the username / password info to the Security header. This is different from adding header info outside of the Security headers. 

The correct way to do this (for custom bindings / authenticationMode="CertificateOverTransport") (as on the .Net framework version 4.6.1), is to add the Client Credentials as usual :

<pre><code> client.ClientCredentials.UserName.UserName = "[username]";
 client.ClientCredentials.UserName.Password = "[password]";
</code></pre>

and then add a "token" in the security binding element - as the username / pwd credentials would not be included by default when the authentication mode is set to certificate.

You can set this token like so:

<pre><code> //Get the current binding 
 System.ServiceModel.Channels.Binding binding = client.Endpoint.Binding;
 //Get the binding elements 
 BindingElementCollection elements = binding.CreateBindingElements();
 //Locate the Security binding element
 SecurityBindingElement security = elements.Find&lt;SecurityBindingElement&gt;();

 //This should not be null - as we are using Certificate authentication anyway
 if (security != null)
 {
 UserNameSecurityTokenParameters uTokenParams = new UserNameSecurityTokenParameters();
 uTokenParams.InclusionMode = SecurityTokenInclusionMode.AlwaysToRecipient;
security.EndpointSupportingTokenParameters.SignedEncrypted.Add(uTokenParams);
 }

 client.Endpoint.Binding = new CustomBinding(elements.ToArray());
</code></pre>

That should do it. Without the above code (to explicitly add the username token), even setting the username info in the client credentials may not result in those credentials passed to the Service.

blocks|key|119417|text|我在web.config中添加了customBinding。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|119418|<configuration>
++<system.serviceModel>
++++<bindings>
++++++<customBinding>
++++++++<binding+name="CustomSoapBinding">
++++++++++<security+includeTimestamp="false"
++++++++++++++++++++authenticationMode="UserNameOverTransport"
++++++++++++++++++++defaultAlgorithmSuite="Basic256"
++++++++++++++++++++requireDerivedKeys="false"
++++++++++++++++++++messageSecurityVersion="WSSecurity10WSTrustFebruary2005WSSecureConversationFebruary2005WSSecurityPolicy11BasicSecurityProfile10">
++++++++++</security>
++++++++++<textMessageEncoding+messageVersion="Soap11"></textMessageEncoding>
++++++++++<httpsTransport+maxReceivedMessageSize="2000000000"/>
++++++++</binding>
++++++</customBinding>
++++</bindings>
++++<client>
++++++<endpoint+address="https://test.com:443/services/testService"
++++++++++++++++binding="customBinding"
++++++++++++++++bindingConfiguration="CustomSoapBinding"
++++++++++++++++contract="testService.test"
++++++++++++++++name="test"+/>
++++</client>
++</system.serviceModel>
++<startup>
++++<supportedRuntime+version="v4.0"
++++++++++++++++++++++sku=".NETFramework,Version=v4.0"/>
++</startup>
</configuration>|code-block|syntax|javascript|119419|添加customBinding后，我可以将用户名和密码传递给客户端服务，如下所示：|119420|service.ClientCridentials.UserName.UserName+=+"testUser";
service.ClientCridentials.UserName.Password+=+"testPass";|119421|通过这种方式，您可以将标头中的用户名和密码传递给SOAP+WCF服务。|119422|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I added customBinding to the web.config. 

<pre><code>&lt;configuration&gt;
 &lt;system.serviceModel&gt;
 &lt;bindings&gt;
 &lt;customBinding&gt;
 &lt;binding name="CustomSoapBinding"&gt;
 &lt;security includeTimestamp="false"
 authenticationMode="UserNameOverTransport"
 defaultAlgorithmSuite="Basic256"
 requireDerivedKeys="false"
 messageSecurityVersion="WSSecurity10WSTrustFebruary2005WSSecureConversationFebruary2005WSSecurityPolicy11BasicSecurityProfile10"&gt;
 &lt;/security&gt;
 &lt;textMessageEncoding messageVersion="Soap11"&gt;&lt;/textMessageEncoding&gt;
 &lt;httpsTransport maxReceivedMessageSize="2000000000"/&gt;
 &lt;/binding&gt;
 &lt;/customBinding&gt;
 &lt;/bindings&gt;
 &lt;client&gt;
 &lt;endpoint address="https://test.com:443/services/testService"
 binding="customBinding"
 bindingConfiguration="CustomSoapBinding"
 contract="testService.test"
 name="test" /&gt;
 &lt;/client&gt;
 &lt;/system.serviceModel&gt;
 &lt;startup&gt;
 &lt;supportedRuntime version="v4.0"
 sku=".NETFramework,Version=v4.0"/&gt;
 &lt;/startup&gt;
&lt;/configuration&gt;
</code></pre>

After adding customBinding, I can pass username and password to client service like as follows:

<pre><code>service.ClientCridentials.UserName.UserName = "testUser";
service.ClientCridentials.UserName.Password = "testPass";
</code></pre>

In this way you can pass username, password in the header to a SOAP WCF Service.

blocks|key|119455|text|如果这与Peoplesoft问题有关：https://support.oracle.com/knowledge/PeopleSoft%2520Enterprise/2370907_1.html|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|119456|我需要在Soap密码上设置属性，而以前没有在该标记上设置该属性。|119457|我只需在我的自定义绑定上设置MessageSecurityVersion：|119458|++CustomBinding+customBinding+=+new+CustomBinding();
++++++++++++customBinding.Name+=+endpointName;
++++++++++++customBinding.CloseTimeout+=+TimeSpan.FromMinutes(1);
++++++++++++customBinding.OpenTimeout+=+TimeSpan.FromMinutes(1);
++++++++++++customBinding.SendTimeout+=+TimeSpan.FromMinutes(20);
++++++++++++customBinding.ReceiveTimeout+=+TimeSpan.FromMinutes(20);

++++++++++++TextMessageEncodingBindingElement+textMessageElement+=+new+TextMessageEncodingBindingElement(MessageVersion.Soap11,+Encoding.UTF8);
++++++++++++customBinding.Elements.Add(textMessageElement);

++++++++++++TransportSecurityBindingElement+securityElement+=+SecurityBindingElement.CreateUserNameOverTransportBindingElement();
++++++++++++securityElement.IncludeTimestamp+=+false;
++++++++++++securityElement.MessageSecurityVersion+=+MessageSecurityVersion.WSSecurity10WSTrustFebruary2005WSSecureConversationFebruary2005WSSecurityPolicy11BasicSecurityProfile10;
++++++++++++customBinding.Elements.Add(securityElement);

++++++++++++//+ORDER+MATTERS:+THIS+HAS+TO+BE+LAST!!!+-+HVT
++++++++++++HttpsTransportBindingElement+transportElement+=+new+HttpsTransportBindingElement();
++++++++++++transportElement.MaxBufferSize+=+int.MaxValue;
++++++++++++transportElement.MaxReceivedMessageSize+=+int.MaxValue;
++++++++++++customBinding.Elements.Add(transportElement);

++++++++++++return+customBinding;|code-block|syntax|javascript|119459|entityMap|0|LINK|mutability|MUTABLE|url|https://support.oracle.com/knowledge/PeopleSoft%2520Enterprise/2370907_1.html^0|J|23|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|10|8|@]|9|@]|C|$K|L]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

If this is in relation to this Peoplesoft issue: <a href="https://support.oracle.com/knowledge/PeopleSoft%20Enterprise/2370907_1.html" rel="nofollow noreferrer">https://support.oracle.com/knowledge/PeopleSoft%20Enterprise/2370907_1.html</a>
I needed to set the attribute on the Soap Password, where previously the attribute was not being set on that tag.
I simply set the MessageSecurityVersion on my Custom Binding:
<pre><code> CustomBinding customBinding = new CustomBinding();
 customBinding.Name = endpointName;
 customBinding.CloseTimeout = TimeSpan.FromMinutes(1);
 customBinding.OpenTimeout = TimeSpan.FromMinutes(1);
 customBinding.SendTimeout = TimeSpan.FromMinutes(20);
 customBinding.ReceiveTimeout = TimeSpan.FromMinutes(20);

 TextMessageEncodingBindingElement textMessageElement = new TextMessageEncodingBindingElement(MessageVersion.Soap11, Encoding.UTF8);
 customBinding.Elements.Add(textMessageElement);

 TransportSecurityBindingElement securityElement = SecurityBindingElement.CreateUserNameOverTransportBindingElement();
 securityElement.IncludeTimestamp = false;
 securityElement.MessageSecurityVersion = MessageSecurityVersion.WSSecurity10WSTrustFebruary2005WSSecureConversationFebruary2005WSSecurityPolicy11BasicSecurityProfile10;
 customBinding.Elements.Add(securityElement);

 // ORDER MATTERS: THIS HAS TO BE LAST!!! - HVT
 HttpsTransportBindingElement transportElement = new HttpsTransportBindingElement();
 transportElement.MaxBufferSize = int.MaxValue;
 transportElement.MaxReceivedMessageSize = int.MaxValue;
 customBinding.Elements.Add(transportElement);

 return customBinding;
</code></pre>

I'm trying to consume a third-party web service
<a href="https://staging.identitymanagement.lexisnexis.com/identity-proofing/services/identityProofingServiceWS/v2?wsdl">https://staging.identitymanagement.lexisnexis.com/identity-proofing/services/identityProofingServiceWS/v2?wsdl</a>

I already added it as a service reference but I'm not sure how to pass the credentials for the header.

How can I make the header request match this format?

<pre class="lang-xml prettyprint-override"><code>&lt;soapenv:Header&gt;
 &lt;wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"&gt;
 &lt;wsse:UsernameToken wsu:Id="UsernameToken-49" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"&gt;
 &lt;wsse:Username&gt;12345/userID&lt;/wsse:Username&gt;
 &lt;wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/ oasis-200401-wss-username-token-profile-1.0#PasswordText"&gt;password123&lt;/wsse:Password&gt;
 &lt;wsse:Nonce EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary"&gt;d+VxCZX1cH/ieMkKEr/ofA==&lt;/wsse:Nonce&gt;
 &lt;wsu:Created&gt;2012-08-04T20:25:04.038Z&lt;/wsu:Created&gt;
 &lt;/wsse:UsernameToken&gt;
 &lt;/wsse:Security&gt;
&lt;/soapenv:Header&gt;
</code></pre>

How can I pass a username/password in the header to a SOAP WCF Service

身份验证

我正在尝试使用第三方web服务我已经将其添加为服务引用，但我不确定如何传递头部的凭据。如何使header请求与此格式匹配？<soapenv:Header> <wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.or...

问如何将标头中的用户名/密码传递给SOAP WCF服务
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何将标头中的用户名/密码传递给SOAP WCF服务EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何将标头中的用户名/密码传递给SOAP WCF服务
EN