Axis2
  1. Axis2
  2. AXIS2-4164

Allow to specify JMS username and password directly via properties in JMS Transport.

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.5
    • Component/s: JMS transport
    • Labels:
      None
    • Environment:
      Axis2 1.4.1 with Tibco EMS.

      Description

      Currently the JMS Transport on client side allows to specify username and password for JNDI access via URL properties. In production environments typically the JMS server also secured with username and password. There has been an improvement to allow to specify JMS username passwords indirectly by referring to corresponding JNDI entries

      • transport.jms.ConnectionFactoryJNDIUser
      • transport.jms.ConnectionFactoryJNDIPass

      For a client only setup, where the JNDI content cannot be configured with these indirect values, it would be useful to set these values directly via the URL.

      The attached patch extends the current code to obtain these values from the properties

      • transport.jms.ConnectionFactoryUser
      • transport.jms.ConnectionFactoryPass
        If these are not set, it falls back to the previous JNDI values.

      The second patch implements the same mechanism for JMSListener on the server side. In this case the properties will be used from axis2.xml similar to the JNDI approach.

      I would appreciate, if you could include this improvement into the next release.

      1. axis141-jms-user.patch2
        2 kB
        Gabor Herr
      2. axis141-jms-user.patch
        2 kB
        Gabor Herr

        Activity

        Gabor Herr created issue -
        Gabor Herr made changes -
        Field Original Value New Value
        Attachment axis141-jms-user.patch [ 12395192 ]
        Gabor Herr made changes -
        Remaining Estimate 0.5h [ 1800 ]
        Original Estimate 0.5h [ 1800 ]
        Description Currently the JMS Transport on client side allows to specify username and password for JNDI access via URL properties. In production environments typically the JMS server also secured with username and password. There has been an improvement to allow to specify JMS username passwords *indirectly* by referring to corresponding JNDI entries
        - transport.jms.ConnectionFactoryJNDIUser
        - transport.jms.ConnectionFactoryJNDIPass

        For a client only setup, where the JNDI content cannot be configured with these indirect values, it would be useful to set these values directly via the URL.

        The attached patch extends the current code to obtain these values from the properties
        - transport.jms.ConnectionFactoryUser
        - transport.jms.ConnectionFactoryPass
        If these are not set, it falls back to the previous JNDI values.

        I hope, you could include this improvement into the next release.
        Currently the JMS Transport on client side allows to specify username and password for JNDI access via URL properties. In production environments typically the JMS server also secured with username and password. There has been an improvement to allow to specify JMS username passwords *indirectly* by referring to corresponding JNDI entries
        - transport.jms.ConnectionFactoryJNDIUser
        - transport.jms.ConnectionFactoryJNDIPass

        For a client only setup, where the JNDI content cannot be configured with these indirect values, it would be useful to set these values directly via the URL.

        The attached patch extends the current code to obtain these values from the properties
        - transport.jms.ConnectionFactoryUser
        - transport.jms.ConnectionFactoryPass
        If these are not set, it falls back to the previous JNDI values.

        The second patch implements the same mechanism for JMSListener on the server side. In this case the properties will be used from axis2.xml similar to the JNDI approach.

        I would appreciate, if you could include this improvement into the next release.
        Gabor Herr made changes -
        Attachment axis141-jms-user.patch2 [ 12395216 ]
        Hide
        Asankha C. Perera added a comment -

        Fixed with WS-Commons transport revision 724432

        Introduced two new parameters
        transport.jms.UserName
        transport.jms.Password

        Show
        Asankha C. Perera added a comment - Fixed with WS-Commons transport revision 724432 Introduced two new parameters transport.jms.UserName transport.jms.Password
        Asankha C. Perera made changes -
        Fix Version/s 1.5 [ 12313476 ]
        Assignee Asankha C. Perera [ asankha ]
        Resolution Fixed [ 1 ]
        Status Open [ 1 ] Resolved [ 5 ]
        Andreas Veithen made changes -
        Component/s JMS transport [ 12320603 ]
        Component/s transports [ 12310111 ]

          People

          • Assignee:
            Asankha C. Perera
            Reporter:
            Gabor Herr
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 0.5h
              0.5h
              Remaining:
              Remaining Estimate - 0.5h
              0.5h
              Logged:
              Time Spent - Not Specified
              Not Specified

                Development