Affects: Release Notes Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000004q5qs&sfdc.override=1 project_key: SOA The customer would like the ability to plugin their own encryption implementation for FilePassword. This would be similar to how the FilePassword mechanism works in the JaasSecurityDomain mbean, but using their own pluggable password encryption mechanism. For instance, in the jbossesb-properties, they would like to specify <property name="org.jboss.soa.esb.services.security.publicKeystorePassword" value="testKeystorePassword"/> using their own plugin implementation. Currently the implementation is hard coded and not pluggable.
Link: Added: This issue is related to JBESB-3555
Per DOC-53797: "The goal of this process is to provide a quick and clear response to the customer - we should respond to the request withing two weeks. The response has to be unambgious - if we have rejected the enhancement a reason needs to be provided; if it is accepted then a release version has to be commited to." Ken, can we please make a decision on this ASAP?
Discussed in SOA PM meeting 10/25/2011. Will try to put this into 5.2. We will need to tell the customer about the change through the ticket, need to add to doc next cycle.
We will allow this into the release. Low risk.
Release Notes Docs Status: Added: Not Yet Documented Affects: Added: Release Notes
Patch committed for ER6.
Link: Added: This issue relates to JBESB-3704
Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Resolved Issue Writer: Added: dlesage Release Notes Text: Added: https://issues.jboss.org/browse/SOA-3012 There is now a pluggable password encryption/decryption mechanism for the ESB's FilePassword. This is similar to how the FilePassword mechanism works in the JaasSecurityDomain mbean, but you can uses your own pluggable password encryption mechanism. For instance, in the jbossesb-properties, you can specify property name="org.jboss.soa.esb.services.security.publicKeystorePassword" value="testKeystorePassword" using your plugin implementation. This improves on the old implementation which was hard-coded and not pluggable.
Verified in ER6