How to handle <default> option in WSS outgoing Signature and Encryption sections about jmeter-wssecurity

[tilln]

The initial values of the dropdown boxes in the plugin UI should be the default values as per WSS. Please advise if this is not the case.
It is not necessary to specify default as this is not a recognized value as in SoapUI.

[tilln]

Hi @CuriousQA
Is this still an issue or can this be closed?

[CuriousQA]

Apologies for the delayed response. I tried the initial values but it still doesn't get through the result.

[tilln]

I just had a quick look through the WSS spec and can't find any default values defined there.
However, SoapUI's defaults translate to wss4j default values, e.g. for signature:

<ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#">
<ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>
<ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>

That doesn't really help resolve your issue I suppose, so let's compare what SoapUI (assuming that works) and this plugin generate.
Perhaps you could provide samples of the wss headers?

[CuriousQA]

<ds:Signature Id="SIG-398" xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
ds:SignedInfo
<ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#">
<ec:InclusiveNamespaces PrefixList="soap" xmlns:ec="http://www.w3.org/2001/10/xml-exc-c14n#"/>
</ds:CanonicalizationMethod>
<ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>
<ds:Reference URI="#TS-396">
ds:Transforms
<ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#">
<ec:InclusiveNamespaces PrefixList="wsse soap" xmlns:ec="http://www.w3.org/2001/10/xml-exc-c14n#"/>
</ds:Transform>
</ds:Transforms>
<ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
ds:DigestValuezBVHWCL5dI3dbECjh5jjCDM5VYg=</ds:DigestValue>
</ds:Reference>
<ds:Reference URI="#id-397">
ds:Transforms
<ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#">
<ec:InclusiveNamespaces PrefixList="" xmlns:ec="http://www.w3.org/2001/10/xml-exc-c14n#"/>
</ds:Transform>
</ds:Transforms>
<ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
ds:DigestValuepoIW7Y/IpOcjz7a1kIGlhTQjjs0=</ds:DigestValue>
</ds:Reference>
</ds:SignedInfo>
ds:SignatureValueYAKsBk6THUwMFXrtRr0Q3Hzrfj7qzhIdUZ8WeZW3D0suO46e6twCCPAcfGrvB0Lm58kJspeXeizmduq3LDn9F48lkvRqL1eO3tV1SS01n/4rU8H70WMnm3zyblycjNfV4NkGwpTQznJHSoFDQ8KnMcfAdK3MQsvBZz5FhyIRilQ=</ds:SignatureValue>
<ds:KeyInfo Id="KI-4B2C50BEB05E6BFD261536604573240318">
<wsse:SecurityTokenReference wsu:Id="STR-4B2C50BEB05E6BFD261536604573240319">
ds:X509Data
ds:X509IssuerSerial
ds:X509IssuerNameCN=service</ds:X509IssuerName>
ds:X509SerialNumber1380226828</ds:X509SerialNumber>
</ds:X509IssuerSerial>
</ds:X509Data>
</wsse:SecurityTokenReference>
</ds:KeyInfo>
</ds:Signature>

-_Encryption part
<xenc:EncryptedData Id="ED-4" Type="http://www.w3.org/2001/04/xmlenc#Content" xmlns:xenc="http://www.w3.org/2001/04/xmlenc#">
<xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#aes128-cbc"/>
<ds:KeyInfo xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
<wsse:SecurityTokenReference wsse11:TokenType="http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#EncryptedKey" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsse11="http://docs.oasis-open.org/wss/oasis-wss-wssecurity-secext-1.1.xsd">
<wsse:Reference URI="#EK-9588191B63F746F59615366045725234"/>

I have tried with the above combinations, but didnot work. Appreciate your assistance in this.

[tilln]

@CuriousQA
First of all, the xml tags are not coming through in normal text, so you may want to enclose xml in three backticks ```

You didn't mention whether your xml is from a (working) SoapUI request or a (failing) Jmeter request.
Can you please clarify and provide both, for comparison.

If you could also provide JMeter log output (start JMeter with command line options -Lorg.apache.wss4j=DEBUG -Lnz.co.breakpoint=DEBUG

[no-response]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.