IBM Support

IT32993: Authentication operations fail if more than one IP address is present in the conname of an LDAP AUTHINFO definition

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 LDAP Authentication operations fail if multiple IP addresses
    without port numbers are present in the CONNAME field of the
    IDPWLDAP AUTHINFO definition in use. In this case authentication
    operations includes administrative defining and altering of MQ
    object authorities, and authenticating new connections.
    .
    Diagnostics show that the queue manager is trying to connect to,
    for example "10.0.0.101,10.0.0.202" which is
    incorrect. In this configuration, it should try 10.0.0.101 and
    then 10.0.0.202.
    .
    13:56:23.668680  103983.17     CONN:000012 --------------{
    zfuLdapFormatConnName
    
    13:56:23.668682  103983.17     CONN:000012     MQSC ConnName
    '10.0.0.101,10.0.0.202' LDAP connection
    '10.0.0.101,10.0.0.202'
    
    13:56:23.668684  103983.17     CONN:000012 --------------}
    zfuLdapFormatConnName rc=OK FunctionTime=4
    

Local fix

  • Add port numbers to each IP address in the list to work around
    this
    issue.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of MQ with an IDPWLDAP AUTHINFO object in use for
    CONNAUTH, who have added multiple IP addresses to the CONNAUTH
    attribute of the AUTHINFO object without specifying port numbers
    for these IP addresses.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A logic error meant that the queue manager failed to correctly
    parse comma-separated IP addresses when no port number was
    present, and treated the entire string as a single connection
    name.
    

Problem conclusion

  • The queue manager's AUTHINFO logic has been corrected to
    correctly parse multiple IP addresses within the CONNAME
    attribute when no port numbers are present.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.2 LTS   9.2.0.3
    v9.x CD    9.2.4
    
    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

    IT32993

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7271

  • Reported release

    914

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-05-27

  • Closed date

    2021-07-02

  • Last modified date

    2021-07-02

  • 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 MP

  • Fixed component ID

    5724H7271

Applicable component levels

  • R914 PSY

       UP

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"914"}]

Document Information

Modified date:
16 July 2021