APAR status
Closed as program error.
Error description
A client application fails to connect to a queue manager with error AMQ9777: Channel was blocked. AMQ9777: Channel was blocked The inbound channel 'A.TO.B' was blocked from address 'abc (xxx.xxx.xxx.xxx)' because the active values of the channel matched a record configured with USERSRC(NOACCESS). The active values of the channel were 'CLNTUSER(xyz) ADDRESS(abc)'. MQ is not matching the MQCSP user against the USERMAP rule above. Instead it is only looking at the ID that the client application process is running under.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: Users of MQCSP to identify and authenticate users may be affected by this problem. Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: When ADOPTCTX(YES) is used on the default authentication information object, IBM MQ was failing to honour a USERMAP rule. For example, with the following channel authentication record definition: SET CHLAUTH('MY.CHLAUTH') TYPE(USERMAP) DESCR('Allow user bob and force CONNAUTH') CLNTUSER('bob') CHCKCLNT(REQUIRED) USERSRC(CHANNEL) When logged in as 'fred', it might be expected that the following command would authenticate as 'bob': runmqsc -c -u bob QMGR In fact, the queue manager uses the logged in user identifier of 'fred'.
Problem conclusion
The fix may break how customers have come to expect this functionality to work so the new behaviour must be enabled via a qm.ini parameter. To have the queue manager use this new behaviour, set the ChlauthEarlyAdopt attribute under the Channels stanza to y or Y, e.g. Channels: ChlauthEarlyAdopt=y If security exits are enabled for the channel then ChlauthEarlyAdopt must be set to 'e' or 'E' otherwise the channel will fail to use the new behaviour. Note that setting ChlauthEarlyAdopt to 'e' or 'E' when security exits are not in use will have the same effect as setting it to 'y' or 'Y'. APAR IT18052 made further changes to the new ChlauthEarlyAdopt parameter and so it is recommended that users review the details of that APAR in combination with this one. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v8.0 8.0.0.5 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
IT12825
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
2015-12-16
Closed date
2016-04-29
Last modified date
2017-03-20
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PI61670
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":"LOB45","label":"Automation"}}]
Document Information
Modified date:
20 March 2017