IBM Support

IT20283: A QPID-JMS 0.20.0 CLIENT, USING AN AMQP CHANNEL TO CONNECT TO THE QUEUE MANAGER, RECEIVES AN MQ AUTHORIZATION ERROR 2035.

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

  • When Qpid-JMS 0.11.1 client attempts to connect via an IBM AMQP
    channel using Simple Authentication and Security Layer (SASL)
    they are able to pass their credentials (through PAM on the OS)
    successfully.
    
    However, when the Qpid-JMS 0.20.0 api is used. the
    authentication fails and the user receives an "MQRC 2035
    MQRC_NOT_AUTHORIZED [condition = amqp:unauthorized-access]
    error.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of:
    
    - The MQ V9 AMQP channel
    
    who have MQ Light or Qpid-JMS client applications that:
    
    - Use SASL authentication when connecting to a queue manager
    using an instance of the AMQP channel.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The new version of the Qpid-JMS client (version 0.20.0) changed
    how SASL data was being flown. The new SASL flows were not
    understood by the IBM AMQP channel, because SASL data was
    expected to arrive with a certain order. Due to this, the
    Qpid-JMS clients were not able to be authorized with the queue
    manager and received the following error:
    
         MQRC 2035 MQRC_NOT_AUTHORIZED [condition =
    amqp:unauthorized-access]
    

Problem conclusion

  • The IBM AMQP channel has been updated so that it is can handle
    the new SASL flow and successfully authorize the Qpid-JMS client
    with the queue manager.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.0 CD    9.0.4
    v9.0 LTS   9.0.0.2
    
    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

    IT20283

  • Reported component name

    IBM MQ BASE M/P

  • Reported component ID

    5724H7261

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-04-19

  • Closed date

    2017-05-22

  • Last modified date

    2017-07-07

  • 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

    IBM MQ BASE M/P

  • Fixed component ID

    5724H7261

Applicable component levels

  • R900 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":"9.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
07 July 2017