Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-2569

Test Enhancements to the databaseStoreType

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • AMQ 7.4.0.CR2
    • AMQ 7.2.2.GA
    • broker-core
    • None
    • 3
    • Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration, User Experience
    • AMQ Broker 2319

      broker encryption does not extend to the databaseStoreType

      No way to add encrypted values particularly the password into the <xsd:complexType name="databaseStoreTypeā€¯>

      also Extend the databaseStoreType to support extraction of username and password without having to enter it all together in the jdbc-connection-url

      also

      Scenario 1: When the broker is unable to connect to the database store an ERROR is dumped in the log.

      The AbstractJDBCDriver.java simply outputs whatever exists in the jdbcConnectionUrl. This violates confidentiality concerns since the username and password is configured as part of the jdbcConnectionUrl.

      Scenario 2: When the broker connects to the database, the log file also shows username and password as part of the Broker Configuration output in the INFO scope

      Options

            mtoth@redhat.com Michal Toth
            mtoth@redhat.com Michal Toth
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - 3 days
                3d
                Remaining:
                Remaining Estimate - 2 days
                2d
                Logged:
                Time Spent - Not Specified Time Not Required
                Not Specified