I am sorry, but I was trying to understand your concern.
I don't understand what you try to express with your initial statement "We have received a feedback from IBM Support Team that logout behavior with BAW BPM process applications with OOTB capability is not available to use which is very surprising."
I asked a simple question twice, but no response. At this point, I don't know how to help.
Original Message:
Sent: Mon October 06, 2025 04:02 AM
From: Ankit Garg
Subject: IBM BAW BPM applications with OOTB logout implementation | Looks OOTB logout capability missing which is a major drawback | Security non-compliances
Hi @Jens Engelke, Your response is not helping, instead looping in circles. With CP4BA 24.0.1 which is a valid supported product, we need a solution for logout behavior which I have mentioned as concern in the primary statement. If product team is expecting that customer will continue to upgrade 25+ and apply fix packs every quarter where core concern is not addressed, is not appreciated.
We expect product to comply security centric all non-functional requirements proactively not like an idea or upgrade from one version to another. I am not concerned about how other customer's understand and perceive this behavior, for us this is not acceptable stating that logout behavior for BPM process applications with BAW is not supported as OOTB behavior. Thank you
------------------------------
Ankit Garg Architect
Original Message:
Sent: Mon October 06, 2025 02:54 AM
From: Jens Engelke
Subject: IBM BAW BPM applications with OOTB logout implementation | Looks OOTB logout capability missing which is a major drawback | Security non-compliances
Hi Ankit,
can you describe the behavior you observe and where it deviates from this documentation?
So far, most customers were actually expecting a single logout experience. This is what we have in 25.0.0.
------------------------------
Jens Engelke
Original Message:
Sent: Sat October 04, 2025 06:29 AM
From: Ankit Garg
Subject: IBM BAW BPM applications with OOTB logout implementation | Looks OOTB logout capability missing which is a major drawback | Security non-compliances
Hi,
We have CP4BA containerized where UMS still an integral part of foundation services.
We expect logout behavior as per https://www.ibm.com/docs/en/baw/24.0.x?topic=service-understanding-user-management-login-logout-behavior for BAW BPM process applications.
Thank you
------------------------------
Ankit Garg Architect
Original Message:
Sent: Sat October 04, 2025 01:40 AM
From: Jens Engelke
Subject: IBM BAW BPM applications with OOTB logout implementation | Looks OOTB logout capability missing which is a major drawback | Security non-compliances
Hi Ankit,
are you using containers or traditional install?
How do you think the product should behave and how is this different from the actual behavior?
You link to user management service documentation, which is an optional component for traditional. It has been removed from containers in 25.0.0.
------------------------------
Jens Engelke
Original Message:
Sent: Thu October 02, 2025 11:03 PM
From: Ankit Garg
Subject: IBM BAW BPM applications with OOTB logout implementation | Looks OOTB logout capability missing which is a major drawback | Security non-compliances
Hi All,
Good morning, evening !!
We have received a feedback from IBM Support Team that logout behavior with BAW BPM process applications with OOTB capability is not available to use which is very surprising. From security governance and compliance perspective, I am wondering how this major drawback left unattended and customer is requested to leverage BAW BPM process for modernized capabilities. I am told to create a idea by support team which I strongly disagree.
There are certain non-functional requirements which product must comply and adhere to, I am wondering how such is suggestion is justified.
Reference which is expected to be complied by the product but I am advised that BAW BPM process does not support that by IBM PMR support team
https://www.ibm.com/docs/en/baw/24.0.x?topic=service-understanding-user-management-login-logout-behavior
Do we have custom implementation reference which depicts the exact logout behavior to implement? Thank you
------------------------------
Ankit Garg Architect
------------------------------