I have developed a SOAP web service using .NET that is to be exposed to client applications via a Windows Azure Service Bus relay. The client application that will be calling the SOAP web service is not based on Microsoft technology and the only authentication method that it can support is HTTP Basic authentication over SSL. It cannot support any WS-* web standards. The plan is to use a custom username/password validator in the service configuration to validate the username/password (passed in the HTTP authentication header) against a custom application database.
I'm having real trouble configuring my SOAP web service to use the basicHttpRelayBinding and Basic authentication. In the service configuration I have set the "Security.Mode" property to "Transport", but the relay binding does not support a "ClientCredentialType" property that I can set to "Basic" to specify that the service expects a Basic authentication header. In fact it seems that none of the relay bindings support a "ClientCredentialType" property. This property exists for the standard non-relay WCF bindings (such as basicHttpBinding) and is how you configure Basic authentication.
Have I missed something here, or do the Azure Relay bindings not support HTTP Basic authentication from the client to the service?
Thanks,
Mark.