glassfish
  1. glassfish
  2. GLASSFISH-11721

GF does not allow all required passwords to be passed to managed MQ broker

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.1
    • Fix Version/s: 4.0_b63
    • Component/s: jms
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

      Description

      A MQ password file allows you to specify

      o keystore password (imq.keystore.password)
      o LDAP repository password (imq.user_repository.ldap.password)
      o JDBC database password (imq.persist.jdbc.password)
      o imqcmd password (imq.imqcmd.password)
      o broker bridge service manager administrator password
      (imq.bridge.admin.password)

      This is normally done by passing a password file to the
      broker. However Glassfish also passes in a password file on the
      command line, which overrides any password file configured in the
      broker properties. Currently, GF does not provide users the option to configure
      and use the above mentioned properties. We need a way to enable this in GF.

        Activity

        Hide
        Simon Meng added a comment -

        Currently, user can set the mq required passwords via GF jms-service properties. GF call setBrokerProps method to pass these properties to jmsra. jmsra can get the required passwords from broker properties.
        GF support password aliases process. That means when setting jms-service properties, user can use plain text or password aliases as propterty value.

        Show
        Simon Meng added a comment - Currently, user can set the mq required passwords via GF jms-service properties. GF call setBrokerProps method to pass these properties to jmsra. jmsra can get the required passwords from broker properties. GF support password aliases process. That means when setting jms-service properties, user can use plain text or password aliases as propterty value.
        Hide
        Tom Mueller added a comment -

        Marking the fix version field as "future-release". This is based on an evaluation by John, Michael, and Tom WRT to the PRD for the Java EE 7 RI/SDK. This issue was deemed to not be a P1 for that release. If this is in error or there are other reasons why this RFE should be targeted for the Java EE 7 RI/SDK release, then change the fix version field back to an appropriate build.

        Show
        Tom Mueller added a comment - Marking the fix version field as "future-release". This is based on an evaluation by John, Michael, and Tom WRT to the PRD for the Java EE 7 RI/SDK. This issue was deemed to not be a P1 for that release. If this is in error or there are other reasons why this RFE should be targeted for the Java EE 7 RI/SDK release, then change the fix version field back to an appropriate build.
        Hide
        Tom Mueller added a comment -

        Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

        Show
        Tom Mueller added a comment - Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.
        Hide
        Nigel Deakin added a comment -

        Following changes to MQ 4.5, Glassfish no longer needs to use a password file to
        pass passwords to the managed broker. Updating issue summary accordingly.

        Show
        Nigel Deakin added a comment - Following changes to MQ 4.5, Glassfish no longer needs to use a password file to pass passwords to the managed broker. Updating issue summary accordingly.

          People

          • Assignee:
            Simon Meng
            Reporter:
            Satish Kumar
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: