Call Java WS from .NET - The Java Path uses Apache Rampart, the equivalent of .NET

Question

The vendor with whom we integrate provides some of the features of the web service ... They developed it in Java and also provided us with an example client project (in Java) that shows the consumption of these web services. We really want to implement the consumption / interface of web services using .NET, but we cannot understand how the security system should work.

In their Java client example, they seem to be using something called "Apache Rampart". They have code inside that looks like this:

public static void initSecurityPolicy(ServiceClient client) throws Exception 
{
    Options options = client.getOptions();
    options.setProperty(RampartMessageData.KEY_RAMPART_POLICY, 
        loadPolicy("policy.xml"));

    options.setUserName(USERID);
    options.setPassword(PASSWD);
    options.setTimeOutInMilliSeconds(READTIMEOUT);
    client.engageModule("rampart"); 
}

- , .NET, ? .NET-.. WSDL-, -, / , " SOAP", , .

policy.xml. .NET-, -, VStudio WS-, , policy.xml, , .NET.

Answer 1

, IKVM Java-. JVM, .NET.

Answer 2

... - :

<soap:Header>
   <wsse:Security soap:mustUnderstand="1" 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-E2E367EC446B10BDA2150463848593046">
         <wsse:Username>User</wsse:Username>
         <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">Pass</wsse:Password>
         <wsse:Nonce EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">/rHCse9+oW6b71t1+J3GPA==</wsse:Nonce>
         <wsu:Created>2017-09-05T09:08:05.930Z</wsu:Created>
      </wsse:UsernameToken>
   </wsse:Security>
</soap:Header>

, UsernameToken .NET SOAP