IBM Support

IT33722: USE DIFFERENT SECURITY IDENTITIES FOR KAFKA NODES WITHIN AN INTGERATION SERVER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as requirement.

Error description

  • By default the Kafka message flow nodes use the single security
    identity called kafka::KAFKA::<server name> for accessing the
    username and password used to connect to the Kafka servers.
    This APAR provides support for each Kafka message flow node to
    use different security identities based upon the value of the
    "Security Identity" field on each of the Kafka nodes which may
    be configured using the BAR editor or the mqsiapplybaroverride
    command.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM App Connect Enterprise V11 using the Kafka
    message flow nodes.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    By default the Kafka message flow nodes use a single security
    identity called kafka::KAFKA::<server name> for accessing the
    username and password used to connect to the Kafka servers.
    Users wishing for more granular level of authorisation are
    required to deploy message flows into separate integration
    servers.
    

Problem conclusion

  • This APAR provides support for each Kafka message flow node to
    use a different security identity based upon the value of the
    "Security Identity" field on each of the Kafka nodes. This
    property may alose be configured using the BAR editor or the
    mqsiapplybaroverride command.
    

Temporary fix

Comments

  • USE DIFFERENT SECURITY IDENTITIES FOR KAFKA NODES WITHIN AN
    INTEGRATION SERVER
    

APAR Information

  • APAR number

    IT33722

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0540

  • Reported release

    A00

  • Status

    CLOSED REQ

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-07-29

  • Closed date

    2021-01-29

  • Last modified date

    2021-01-29

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0"}]

Document Information

Modified date:
30 January 2021