APAR status
Closed as program error.
Error description
In order to use the Kafka Nodes with Kerberos authentication it is required to set the SASL mechanism to GSSAPI, however the nodes will attempt to autoamtically set the SASL mechanism based on the security method. Since the default is username / pasword authentication this prevent the use of Kerberos. This APAR introduces a new environment variable MQSI_KAFKA_SASL_MECHANISM when set in the Integration node's profile environment the value will be passed through to the "sasl.mechanism" property of the Kafka client. In order to use Kerberos the following setting should be used: MQSI_KAFKA_SASL_MECHANISM=GSSAPI
Local fix
Problem summary
**************************************************************** USERS AFFECTED: All users of Integration Bus v10, or App Connect Enterprise v11 using the Kafka Nodes. Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: In order to use the Kafka Nodes with Kerberos authentication it is required to set the SASL mechanism to GSSAPI, however the nodes will attempt to autoamtically set the SASL mechanism based on the security method. Since the default is username / password authentication, this prevents the use of Kerberos.
Problem conclusion
This APAR introduces a new environment variable MQSI_KAFKA_SASL_MECHANISM which when set in the Integration node's profile environment, the value will be passed through to the "sasl.mechanism" property of the Kafka client. In order to use Kerberos the following setting should be used: MQSI_KAFKA_SASL_MECHANISM=GSSAPI This APAR also introduces the ability to pass a Kafka properties file directly in to the Node. For a producer you can set the fully qualified path to the properties file in MQTT configurable service or policy for a consumer the fully qualified path should be set in property2. The properties file itself can include any properties recognised by the Kafka client including the SASL Mechanism and the requires jaas.conf stanza. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v10.0 10.0.0.12 v11.0 11.0.0.1 The latest available maintenance can be obtained from: http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 If the maintenance level is not yet available,information on its planned availability can be found on: http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IT24150
Reported component name
INTEGRATION BUS
Reported component ID
5724J0540
Reported release
A00
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-02-21
Closed date
2018-09-19
Last modified date
2019-01-08
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
INTEGRATION BUS
Fixed component ID
5724J0540
Applicable component levels
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
08 January 2019