IBM Support

IT40485: SASL.JAAS.CONFIG PROPERTY MAY NOT WORK FOR KAFKA NODES.

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

  • A user can specify the authentication login module through
    sasl.jaas.config Kafka client property. It can be configured
    through an external properties file or by using a Kafka policy.
    However, all the values of sasl.jaas.config may not take effect
    and the user will see the Kafka nodes failing to connect to the
    Kafka server.
    
    In the reported case, the customer was trying to connect to an
    Amazon MSK server protected with IAM policy and they were using
    the following properties file on the KafkaConsumer node.
    .
    ssl.truststore.location=<PATH_TO_TRUST_STORE_FILE>
    security.protocol=SASL_SSL
    sasl.mechanism=AWS_MSK_IAM
    sasl.jaas.config=software.amazon.msk.auth.iam.IAMLoginModule
    required;
    sasl.client.callback.handler.class=software.amazon.msk.auth.iam
    .IAMClientCallbackHandler
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM App Connect Enterprise V12.0 and V11.0 using
    sasl.jaas.config property with Kafka nodes.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A user can specify the authentication login module through
    sasl.jaas.config Kafka client property. It can be configured
    through an external properties file or by using the SASL Config
    property of a Kafka policy. However, the value of
    sasl.jaas.config may not take effect and the user will see the
    Kafka nodes failing to connect to the Kafka server.
    
    In the reported case, the customer was trying to connect to an
    Amazon MSK server protected with IAM policy and they were using
    an external properties file on the KafkaConsumer node that
    contains the following values.
    
    ssl.truststore.location=<PATH_TO_TRUST_STORE_FILE>
    security.protocol=SASL_SSL
    sasl.mechanism=AWS_MSK_IAM
    sasl.jaas.config=software.amazon.msk.auth.iam.IAMLoginModule
    required;
    sasl.client.callback.handler.class=software.amazon.msk.auth.iam.
    IAMClientCallbackHandler
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT40485

  • Reported component name

    APP CONNECT ENT

  • Reported component ID

    5724J0550

  • Reported release

    B00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-04-01

  • Closed date

    2022-10-27

  • Last modified date

    2022-10-27

  • 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

    APP CONNECT ENT

  • Fixed component ID

    5724J0550

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 October 2022