[
https://issues.apache.org/jira/browse/RAMPART-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12551005
]
Hans G Knudsen commented on RAMPART-78:
---------------------------------------
Hi!
In RampartEngine it seems that encryptionCrypto must be swapped with
signatureCrypto
in the 'processSecurityHeader' call
results = engine.processSecurityHeader(rmd.getDocument(),
actorValue,
tokenCallbackHandler,
encryptionCrypto,
signatureCrypto);
If we asume that :
signatureCrypto = keystore with my privatekey and certificate
encryptionCrypto = keystore with other peoples certificate(s) path
> Rampart ignores the ramp:encryptionCypto
> ----------------------------------------
>
> Key: RAMPART-78
> URL: https://issues.apache.org/jira/browse/RAMPART-78
> Project: Rampart
> Issue Type: Bug
> Components: rampart-policy
> Affects Versions: 1.1, 1.2, 1.3
> Reporter: Abdelaziz Samari
>
> It seems that rampart ignores the ramp:encryptionCypto in the
> ramp:RampartConfig assertion.
> Theire is no implementation concerning the encryptionCypto in the class
> RampartConfigBuilder.
> I suggest to add th following code in the method build of the class
> RampartConfigBuilder:
> //encryptionCypto
> childElement = element.getFirstChildWithName(new
> QName(RampartConfig.NS, RampartConfig.ENCR_CRYPTO_LN));
>
> if (childElement != null) {
> rampartConfig.setEncrCryptoConfig((CryptoConfig) factory
> .build(childElement.getFirstElement()));
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
