Uploaded image for project: 'JBoss Enterprise SOA Platform'
  1. JBoss Enterprise SOA Platform
  2. SOA-3012

Allow for pluggable password encryption/decryption mechanism for FilePassword in esb

    XMLWordPrintable

    Details

    • Type: Feature Request
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 5.0.2, 5.1.0 GA
    • Fix Version/s: 5.2.0.ER6
    • Component/s: JBossESB
    • Labels:
      None
    • Affects:
      Release Notes
    • Release Notes Text:
      Hide
      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.
      Show
      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.
    • Release Notes Docs Status:
      Documented as Resolved Issue

      Description

      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.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  tcunning Tom Cunningham
                  Reporter:
                  rhn-support-mattd Matt Davis
                  Writer:
                  David Le Sage
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: