IBM Support

JR62497: POSSIBLE AUTHENTICATION ERROR IN WORKFLOW CASE EMITTER WHEN SASL SCRAM IS USED

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

  • Authenticating a Kafka user by using SASL SCRAM might fail with
    the following stack trace when the IBM Workflow BPMN emitter
    and the IBM Workflow Case event emitter are both enabled and
    send events to IBM Business Automation Insights:
    java.util.concurrent.ExecutionException:
    org.apache.kafka.common.errors.SaslAuthenticationException: An
    error: (java.security.PrivilegedActionException:
    javax.security.sasl.SaslException: User name could not be
    obtained [Caused by
    javax.security.auth.callback.UnsupportedCallbackException:
    Unrecognized SASL ClientCallback]) occurred when evaluating SASL
    token received from the Kafka Broker. Kafka Client will go to
    AUTHENTICATION_FAILED state.
        at
    org.apache.kafka.clients.producer.KafkaProducer$FutureFailure.<i
    nit>(KafkaProducer.java:1150)
        at
    org.apache.kafka.clients.producer.KafkaProducer.doSend(KafkaProd
    ucer.java:846)
        at
    org.apache.kafka.clients.producer.KafkaProducer.send(KafkaProduc
    er.java:784)
        at
    com.ibm.dba.bai.events.kafka.Transport.send(Transport.java:234)
        at
    com.ibm.dba.bai.events.kafka.Transport.send(Transport.java:209)
        at
    com.ibm.dba.bai.events.icm.transport.kafka.OutputToKafkaTranspor
    t.sendEventNoRetrying(OutputToKafkaTransport.java:320)
        at
    com.ibm.dba.bai.events.icm.transport.kafka.OutputToKafkaTranspor
    t.sendEvent(OutputToKafkaTransport.java:303)
        at
    com.ibm.dba.bai.events.icm.transport.kafka.OutputToKafkaTranspor
    t.sendEvent(OutputToKafkaTransport.java:296)
        at
    com.ibm.dba.bai.events.icm.transport.kafka.OutputToKafkaTranspor
    t.sendEventsBatch(OutputToKafkaTransport.java:240)
        at
    com.ibm.dba.bai.events.icm.transport.kafka.OutputToKafkaTranspor
    t.sendEvents(OutputToKafkaTransport.java:226)
        at
    com.ibm.dba.bai.events.icm.transport.IcmBusinessEventOutputCompo
    site.sendEvents(IcmBusinessEventOutputComposite.java:62)
        at
    com.ibm.dba.bai.events.icm.IcmBusinessEventSdk.emit(IcmBusinessE
    ventSdk.java:154)
        at
    com.ibm.oi.icm.event.emitter.IcmOiEmitter.emitOutput(IcmOiEmitte
    r.java:167)
        at
    com.ibm.oi.icm.event.emitter.IcmOiEmitter.run(IcmOiEmitter.java:
    117)
    

Local fix

Problem summary

  • YOU MIGHT SEE AN AUTHENTICATION ERROR IN THE IBM WORKFLOW CASE
    EVENT EMITTER WHEN USING SASL SCRAM
    

Problem conclusion

  • A fix is available   or will be available that allows
    authentication by using SASL SCRAM for both the IBM workflow
    Case event  emitter and the BPM emitter
    

Temporary fix

  • Not Applicable
    

Comments

APAR Information

  • APAR number

    JR62497

  • Reported component name

    BUS AUTO WORKFL

  • Reported component ID

    5737H4100

  • Reported release

    K00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-07-16

  • Closed date

    2020-08-24

  • Last modified date

    2020-08-24

  • 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

    BUS AUTO WORKFL

  • Fixed component ID

    5737H4100

Applicable component levels

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

Document Information

Modified date:
14 December 2020