IBM Support

IT21306: Ensure consistency among mechanisms for enabling MQCSP authentication mode in Java

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • MQ Classes for Java and Classes for JMS offer multiple
    mechanisms
    to enable MQCSP authentication mode and these mechanisms
    are not consistent in the values they accept to enable the mode.
    
    For instance the MQCSP authentication mode can be enabled
    programmatically in MQ Classes for JMS and MQ Classes for Java
    applications or it can be enabled by setting the Java system
    property: -Dcom.ibm.mq.cfg.jmqi.useMQCSPauthentication.
    
    The MQCSP authentication mode is set programmatically in
    MQ Classes for JMS and MQ Classes for Java applications
    using the properties:
    
      # JMS applications:
      JmsConstants.USER_AUTHENTICATION_MQCSP
    
      # MQ Classes for Java
      MQConstants.USE_MQCSP_AUTHENTICATION_PROPERTY
    
    Both these properties take a boolean "true" or "false" value
    which is inconsistent with the JRE's global
    "-Dcom.ibm.mq.cfg.jmqi.useMQCSPauthentication" property
    which must be set to one of the values "Y" or "N".
    
    The solution for this is to provide support for the values
    "true" and "false" in addition to the current "Y" and "N" for
    the command line property.  For consistency the values
    "true" and "false" are preferred and will be the values
    documented in the knowledge center here:
    
    https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_8.0.0/com.
    ibm.mq.sec.doc/q118680_.htm
    

Local fix

  • To use a supported mechanism (i.e., command line property, or
    the appropriate programming construct)
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of MQ V8 (or later) classes for Java or
    MQ classes for JMS who set the MQCSP authentication mode using
    the Java system property
    <i>-Dcom.ibm.mq.cfg.jmqi.useMQCSPauthentication</i>.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The MQ Classes for Java and Classes for JMS offer multiple
    mechanisms
    to enable MQCSP authentication mode and these mechanisms
    are not consistent in the values they accept to enable the mode.
    
    For instance, the MQCSP authentication mode can be enabled
    programmatically in MQ classes for JMS and MQ classes for Java
    applications or it can be enabled by setting the Java system
    property: -Dcom.ibm.mq.cfg.jmqi.useMQCSPauthentication.
    
    The MQCSP authentication mode is set programmatically in
    MQ classes for JMS and MQ classes for Java applications
    using the properties:
    
      # JMS applications:
      JmsConstants.USER_AUTHENTICATION_MQCSP
    
      # MQ Classes for Java
      MQConstants.USE_MQCSP_AUTHENTICATION_PROPERTY
    
    Both these properties take a boolean "true" or "false" value.
    
    This is inconsistent with the global Java system property
    "-Dcom.ibm.mq.cfg.jmqi.useMQCSPauthentication", which must
    be set to one of the values "Y" or "N".
    

Problem conclusion

  • The MQ classes for Java and classes for JMS have been updated so
    that
    the Java system property
    "-Dcom.ibm.mq.cfg.jmqi.useMQCSPauthentication"
    can be set to the values "true" and "false" for consistency with
    the other
    mechanisms for enabling MQCSP authentication mode.
    
    The "-Dcom.ibm.mq.cfg.jmqi.useMQCSPauthentication" property also
    allows
    the values "Y" and "N", for backward compatibility.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.8
    v9.0 LTS   9.0.0.3
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT21306

  • Reported component name

    WMQ BASE MULTIP

  • Reported component ID

    5724H7251

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-07-05

  • Closed date

    2017-07-21

  • Last modified date

    2017-07-21

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    WMQ BASE MULTIP

  • Fixed component ID

    5724H7251

Applicable component levels

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.0.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
21 July 2017