blocks|key|1502940|text|看起来您只能在实例化周期的早期访问这些属性。如果我覆盖代理类(ServerClient)中的构造函数，我就能够设置这些属性：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1502941|base.ClientCredentials.UserName.UserName+=+"Sample";|code-block|syntax|javascript|1502942|我开始感谢那些建议不要使用VS提供的自动构建代理的人。|1502943|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

It appears that you can only access these properties pretty early in the instanciation cycle. If I override the constructor in the proxy class (ServerClient), I'm able to set these properties:

<pre><code>base.ClientCredentials.UserName.UserName = "Sample";
</code></pre>

I'm beginning to appreciate the people who suggest not using the automatically built proxies provided by VS.

blocks|key|1718476|text|我注意到，在为服务创建代理类的实例后，我可以设置一次用户名和密码而不会出错，并成功调用我的set服务。然后，当我尝试在现有实例上再次设置用户名和密码时(当然不必要)，我得到您提到的'Object+is+Read-Only‘错误。为每个实例生命周期设置一次值对我来说很有效。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1718477|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I noticed that after creating an instance of the proxy class for the service, I can set the Username and Password once without errors and do a successful call to my webservice. When I then try to set the Username and Password again on the existing instance (unnecessary of course) I get the 'Object is Read-Only' error you mentioned. Setting the values once per instance lifetime worked for me.

blocks|key|1718175|text|以下是解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1718176|using+SysSvcmod+=+System.ServiceModel.Description;

SysSvcmod.ClientCredentials+clientCredentials+=+new+SysSvcmod.ClientCredentials();
clientCredentials.UserName.UserName+=+"user_name";
clientCredentials.UserName.Password+=+"pass_word";

m_client.ChannelFactory.Endpoint.Behaviors.RemoveAt(1);
m_client.ChannelFactory.Endpoint.Behaviors.Add(clientCredentials);|code-block|syntax|javascript|1718177|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

here is the solution:

<pre><code>using SysSvcmod = System.ServiceModel.Description;

SysSvcmod.ClientCredentials clientCredentials = new SysSvcmod.ClientCredentials();
clientCredentials.UserName.UserName = "user_name";
clientCredentials.UserName.Password = "pass_word";

m_client.ChannelFactory.Endpoint.Behaviors.RemoveAt(1);
m_client.ChannelFactory.Endpoint.Behaviors.Add(clientCredentials);
</code></pre>

blocks|key|1503025|text|我有类似的代码，可以很好地通过UserName：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1503026|++FooServiceClient+client+=+new+FooServiceClient("BasicHttpBinding_IFooService");
++client.ClientCredentials.UserName.UserName+=+"user";
++client.ClientCredentials.UserName.Password+=+"password";|code-block|syntax|javascript|1503027|尝试在app.config中使用绑定名称创建代理。|1503028|entityMap^0|F|8|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

I have similar code that's passing <code>UserName</code> fine:

<pre><code> FooServiceClient client = new FooServiceClient("BasicHttpBinding_IFooService");
 client.ClientCredentials.UserName.UserName = "user";
 client.ClientCredentials.UserName.Password = "password";
</code></pre>

Try creating the proxy with binding name in app.config.

blocks|key|1503415|text|正确的语法是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1503416|//+Remove+the+ClientCredentials+behavior.
client.ChannelFactory.Endpoint.Behaviors.Remove<ClientCredentials>();

//+Add+a+custom+client+credentials+instance+to+the+behaviors+collection.
client.ChannelFactory.Endpoint.Behaviors.Add(new+MyClientCredentials());|code-block|syntax|javascript|1503417|http://msdn.microsoft.com/en-us/library/ms730868.aspx|offset|length|1503418|这对我很管用。|1503419|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|1H|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|U|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|V|8|@]|9|@$I|W|J|X|1|Y]]|A|$]]|$1|K|3|L|5|6|7|Z|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|H]]]]

The correct syntax is:

<pre><code>// Remove the ClientCredentials behavior.
client.ChannelFactory.Endpoint.Behaviors.Remove&lt;ClientCredentials&gt;();

// Add a custom client credentials instance to the behaviors collection.
client.ChannelFactory.Endpoint.Behaviors.Add(new MyClientCredentials());
</code></pre>

<a href="http://msdn.microsoft.com/en-us/library/ms730868.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/ms730868.aspx</a>

It worked for me.

blocks|key|1503476|text|我也面临着同样的问题，当我更改代码时，我的代码开始工作，例如，在初始化客户端对象后立即为客户端凭据赋值。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1503477|这就是解决方案，|1503478|ProductClient+Manager+=+new++ProductClient();++++
Manager.ClientCredentials.UserName.UserName+=+txtUserName.Text;
Manager.ClientCredentials.UserName.Password+=+txtPassword.Text;|code-block|syntax|javascript|1503479|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I was facing same problem, my code started working when I changed my code i.e. assigning values to Client credential immediately after initializing Client object.

here is the solution ,

<pre><code>ProductClient Manager = new ProductClient(); 
Manager.ClientCredentials.UserName.UserName = txtUserName.Text;
Manager.ClientCredentials.UserName.Password = txtPassword.Text;
</code></pre>

blocks|key|1503512|text|如果通过->添加服务引用->高级->+Add+Web+Reference->+Url/wsdl+(本地磁盘文件)添加服务引用，则不会发生这种情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1503513|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

This will not happen if the service reference is added through -> Add service reference ->Advanced->Add Web Reference-> Url/wsdl (local disk file).

blocks|key|1503567|text|当我试图创建一个泛型方法来为不同的端点创建客户端时，我就遇到了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1503568|下面是我如何做到这一点的。|1503569|++++public+static+T+CreateClient<T>(string+url)+where+T+:+class
++++{
++++++++EndpointAddress+endPoint+=+new+EndpointAddress(url);
++++++++CustomBinding+binding+=+CreateCustomBinding();

++++++++T+client+=+(T)Activator.CreateInstance(typeof(T),+new+object[]+{+binding,+endPoint+});
++++++++SetClientCredentials(client);

++++++++return+client;
++++}

++++public+static+void+SetClientCredentials(dynamic+obj)
++++{
++++++++obj.ChannelFactory.Endpoint.Behaviors.Remove<ClientCredentials>();
++++++++obj.ChannelFactory.Endpoint.Behaviors.Add(new+CustomCredentials());

++++++++obj.ClientCredentials.UserName.UserName+=+"UserId";
++++++++obj.ClientCredentials.UserName.Password+=+"Password";
++++}|code-block|syntax|javascript|1503570|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I was facing this issue where I was trying to create a generic method to create a clients for different end points.

Here how I achieved this.

<pre><code> public static T CreateClient&lt;T&gt;(string url) where T : class
 {
 EndpointAddress endPoint = new EndpointAddress(url);
 CustomBinding binding = CreateCustomBinding();

 T client = (T)Activator.CreateInstance(typeof(T), new object[] { binding, endPoint });
 SetClientCredentials(client);

 return client;
 }

 public static void SetClientCredentials(dynamic obj)
 {
 obj.ChannelFactory.Endpoint.Behaviors.Remove&lt;ClientCredentials&gt;();
 obj.ChannelFactory.Endpoint.Behaviors.Add(new CustomCredentials());

 obj.ClientCredentials.UserName.UserName = "UserId";
 obj.ClientCredentials.UserName.Password = "Password";
 }
</code></pre>

blocks|key|1502873|text|我认为您的问题可能与InstanceContext的使用有关。我认为这只是服务器端的双工通信通道所需要的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1502874|我承认我不确定这一点，但我认为在这种情况下，您告诉客户端使用现有的实例上下文，这样它就会认为已经有一个正在运行的服务，不允许更改。|1502875|是什么推动了InstanceContext的使用？|1502876|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I think your problem might be related to the use of the InstanceContext. I thought that was only needed for duplex communication channels from the server side. 

I admit I'm not sure about this, but I think in this case you are telling the client to use an existing instance context so it thinks there is already a running service and will not allow changes.

What is driving the use of InstanceContext?

blocks|key|1503175|text|如果使用双工客户端，则在实例化它时，将使用现有凭据初始化从中派生客户端的DuplexClientBase中的DuplexChannelFactory，以便它可以打开回调通道，这就是为什么凭据将是只读的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1503176|我补充了迈克的问题，如果你不打算使用NetTcpBinding固有的传输层安全性，为什么要使用它呢？也许基于HTTP的绑定会更合适？这将允许您使用基于证书的安全性，我相信它可以在实例化(http://msdn.microsoft.com/en-us/library/ms576164.aspx)之后进行修改。|offset|length|1503177|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/ms576164.aspx^0|0|2L|1H|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

If using a duplex client, when you instantiate it the DuplexChannelFactory within the DuplexClientBase that your client is derived from is initialized with existing credentials so it can open the callback channel, which is why the credentials would be read only.

I second Mike's question and also ask why are you using NetTcpBinding if you are not going to use its inherent transport level security? Perhaps an HTTP based binding would be a better fit? That would allow you to use certificate based security which I believe can be modified after instantiation (<a href="http://msdn.microsoft.com/en-us/library/ms576164.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/ms576164.aspx</a>).

blocks|key|1718394|text|虚张声势，但netTcpBinding允许用户名和密码验证吗？尝试使用使用http绑定的应用层(SOAP)安全性|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1718395|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

A shot in the dark but does netTcpBinding allow username and password validation? Try using application layer (SOAP) security using a http binding

blocks|key|1718761|text|或者您可以简单地检查凭据|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1718762|++++if+(client.ClientCredentials.ClientCertificate.Certificate+==+null+%7C%7C+string.IsNullOrEmpty(client.ClientCredentials.ClientCertificate.Certificate.Thumbprint))
++++{
++++++++client.ClientCredentials.ClientCertificate.SetCertificate(
++++++++++++StoreLocation.LocalMachine,
++++++++++++StoreName.My,
++++++++++++X509FindType.FindByThumbprint,+ConfigurationManager.AppSettings.Get("CertificateThumbprint"));
++++}|code-block|syntax|javascript|1718763|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

or you could just simply check the Credentials

<pre><code> if (client.ClientCredentials.ClientCertificate.Certificate == null || string.IsNullOrEmpty(client.ClientCredentials.ClientCertificate.Certificate.Thumbprint))
 {
 client.ClientCredentials.ClientCertificate.SetCertificate(
 StoreLocation.LocalMachine,
 StoreName.My,
 X509FindType.FindByThumbprint, ConfigurationManager.AppSettings.Get("CertificateThumbprint"));
 }
</code></pre>

I have a proxy object generated by Visual Studio (client side) named ServerClient. I am attempting to set ClientCredentials.UserName.UserName/Password before opening up a new connection using this code:

<pre><code>InstanceContext context = new InstanceContext(this);

m_client = new ServerClient(context);
m_client.ClientCredentials.UserName.UserName = "Sample";
</code></pre>

As soon as the code hits the UserName line it fails with an "Object is read-only" error. I know this can happen if the connection is already open or faulted, but at this point I haven't called context.Open() yet. 

I have configured the Bindings (which uses netTcpBinding) to use Message as it's security mode, and MessageClientCredentialType is set to UserName.

Any ideas?

Getting "Object is read only" error when setting ClientCredentials in WCF

Visual Studio

服务器

我有一个由Visual Studio (客户端)生成的名为ServerClient的代理对象。在使用以下代码打开新连接之前，我正在尝试设置ClientCredentials.UserName.UserName/Password：InstanceContext context = new InstanceContext(this);m_client = new ServerClient(contex

问在WCF中设置ClientCredentials时出现"Object is read only“错误
EN

回答 12

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在WCF中设置ClientCredentials时出现"Object is read only“错误EN

回答 12

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在WCF中设置ClientCredentials时出现"Object is read only“错误
EN