IBM Support

IT45968: Connection from a backlevel client sending an MQCSP structure isrejected when PasswordProtection=warn

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

  • In some scenarios - for example if a channel security exit is
    used - it is valid for a remote IBM MQ client earlier than
    version 8 to provide user credentials to the queue manager
    using an MQCSP flow.
    
    In this scenario, if the non default option
    PasswordProtection=warn is configured in the qm.ini file, an
    AMQ9297W warning message is generated in the queue manager
    error log as expected, but the connection is terminated.
    
    A failure data capture record (FDC) with probe ID RN107010 is
    generated by the amqrmppa process with the reason code
    rrcE_BAD_PARAMETER.
    

Local fix

  • Update the remote client library to a supported version of IBM
    MQ, or configure the channel to use SSL/TLS.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of IBM MQ who have set PasswordProtection=warn in the
    queue manager configuration file (qm.ini) and are connecting an
    application using an MQ client older than version 8 which is
    supplying username and password credentials via an MQCSP
    structure.
    
    As the password protection capability is only applicable to
    cleartext connections, the issue is not seen for clients using
    an SSL/TLS connection to the queue manager.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A logic error without the PasswordProtection=warn logic branch
    meant that the connection was incorrectly terminated with a
    protocol error, instead of being allowed to continue running
    after the AMQ9297W warning message was issued.
    

Problem conclusion

  • The logic error has been corrected in this scenario, so that the
    connection is accepted by the queue manager after the AMQ9297W
    warning message is issued.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.3 LTS   9.3.0.20
    v9.4 LTS   9.4.0.0
    
    The latest available maintenance can be obtained from
    'IBM MQ Recommended Fixes'
    https://www.ibm.com/support/pages/recommended-fixes-ibm-mq
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'IBM MQ
    Planned Maintenance Release Dates'
    https://ibm.biz/mqplannedmaintenance
    
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT45968

  • Reported component name

    MQ BASE V9.3

  • Reported component ID

    5724H7291

  • Reported release

    930

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-04-18

  • Closed date

    2024-04-23

  • Last modified date

    2024-05-14

  • 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

    MQ BASE V9.3

  • Fixed component ID

    5724H7291

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"930","Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"}}]

Document Information

Modified date:
14 May 2024