具有 .NET 2.0 和 Java 客户端的 WCF 服务

发布于 2024-08-13 01:29:42 字数 1025 浏览 3 评论 0原文

我的 WCF 服务是通过 .NET 3.5 完成的，我在实现服务时使用了 wsHttpBinding。

对于 .NET 3.5 客户端，没有问题，但 .NET 2.0 和 Java 客户端在 wsHttpBinding 中存在问题。

因此，我添加了一个带有 basicHttpBinding 的新端点，其安全性与 wsHttpBinding 类似，并考虑以下标准：

我想在启用传输安全性的情况下使用自定义用户名/密码验证。
无法进行 Windows 身份验证。
我不想将自定义标头添加到 SOAP 消息中以进行身份验证。

我的基本HttpBinding配置是：

<basicHttpBinding>
            <binding name="MyService.basicSecureBinding">                                       
                <security mode="TransportWithMessageCredential">
                    <transport clientCredentialType="None" proxyCredentialType="None"/>
                    <message clientCredentialType="UserName" algorithmSuite="Basic128"/>
                </security>
            </binding>
        </basicHttpBinding>

并在ServiceBehavior中声明自定义UsernameValidator类。

但似乎“TransportWithMessageCredential”不能从.NET 2.0客户端使用为了启用自定义用户名验证，消息安全是必要的。

您有什么建议或参考来解决这个问题吗？

原文

My WCF Service is complete with .NET 3.5 and I used wsHttpBinding while implementing my service.

For .NET 3.5 clients, there were no problems, but .NET 2.0 and Java Clients had issues in wsHttpBinding.

So I added a new endpoint with basicHttpBinding with similar security as wsHttpBinding with following criteria in mind:

I would like to use Custom Username/PasswordValidation, while Transport Security is enabled.
Windows authentication is not possible.
I would rather not to add custom Headers to the SOAP messages for authentication.

My basicHttpBinding Configuration is:

<basicHttpBinding>
            <binding name="MyService.basicSecureBinding">                                       
                <security mode="TransportWithMessageCredential">
                    <transport clientCredentialType="None" proxyCredentialType="None"/>
                    <message clientCredentialType="UserName" algorithmSuite="Basic128"/>
                </security>
            </binding>
        </basicHttpBinding>

and in ServiceBehavior Custom UsernameValidator Class is declared.

But it seems that "TransportWithMessageCredential" cannot be used from .NET 2.0 clients
and in order to enable custom username validation, Message security is necessary.

Do you have any suggestions or references to solve this issue?

分享到QQ

分享到微博