[
https://issues.apache.org/jira/browse/WSS-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12703066#action_12703066
]
Colm O hEigeartaigh commented on WSS-177:
-----------------------------------------
Here's a sample output of a test-case in WSS4J for this:
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
<SOAP-ENV:Header>
<wsse:Security
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";
SOAP-ENV:mustUnderstand="1">
<xenc:ReferenceList
xmlns:xenc="http://www.w3.org/2001/04/xmlenc#";>
<xenc:DataReference URI="#EncDataId-8" />
</xenc:ReferenceList>
</wsse:Security>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<xenc:EncryptedData
xmlns:xenc="http://www.w3.org/2001/04/xmlenc#";
Id="EncDataId-8"
Type="http://www.w3.org/2001/04/xmlenc#Content";>
<xenc:EncryptionMethod
Algorithm="http://www.w3.org/2001/04/xmlenc#aes128-cbc";
xmlns:xenc="http://www.w3.org/2001/04/xmlenc#";
/>
<ds:KeyInfo
xmlns:ds="http://www.w3.org/2000/09/xmldsig#";>
<wsse:SecurityTokenReference
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";>
<wsse:KeyIdentifier
EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary";
ValueType="http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#EncryptedKeySHA1";>
EbIUn6SjlFT1/QEEhzWgIzpnsZM=
</wsse:KeyIdentifier>
</wsse:SecurityTokenReference>
</ds:KeyInfo>
<xenc:CipherData
xmlns:xenc="http://www.w3.org/2001/04/xmlenc#";>
<xenc:CipherValue
xmlns:xenc="http://www.w3.org/2001/04/xmlenc#";>
VrSHpA2ITkTAf5Xaa2XANyjt6N2wcWWaPvFsCg8FSuIn3A+MEPGi1mck8GDYfqO6900cQF0VEc3E
0sbZuVS6YkPNeGr7bZQLLVJB4qeWCSsFYMVDHIoS9Jvz0MN2OVovIjLUtlbHg069ajK6YSEw9QlC
DppnU9Q5/y5NsvrYWJseENs18BWN5BAjcWiFoEG1iKfZ2Cq7N2hV/AmqDPlHvrOpgu8CridxfFkP
eR9dJ2ouFaJT0KVnwbNfEmXQVMJPZN9RLnkL5AB1LT+/7LXd/F60119qvDtGm53/CZnI9WtC/aVA
kfWQW3Zug77upu8+TRpuo1kCM85l5diSYSkwQVfaxyrB8+Sgj8kv6dvzy78=
</xenc:CipherValue>
</xenc:CipherData>
</xenc:EncryptedData>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
> Allow encryption using a symmetric key and EncryptedKeySHA1
> -----------------------------------------------------------
>
> Key: WSS-177
> URL: https://issues.apache.org/jira/browse/WSS-177
> Project: WSS4J
> Issue Type: Improvement
> Components: WSS4J Core
> Affects Versions: 1.5.7
> Reporter: Colm O hEigeartaigh
> Assignee: Colm O hEigeartaigh
> Fix For: 1.5.8, 1.6
>
>
> This task is to allow WSSecEncrypt to take in a SecretKey object, and use it
> to encrypt data, without generating an ephemeral key or encrypting the
> SecretKey into an EncryptedKey element. The SecretKey is added using
> EncryptedKeySHA1.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
