<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
<channel>
<title>IBM BAW Tips Q&amp;A - Recent questions tagged zen</title>
<link>https://bpm.tips/tag/zen</link>
<description>Powered by Question2Answer</description>
<item>
<title>How are users and groups managed on Cloud Pak for Business Automation compared to WebSphere LDAP in traditional BAW?</title>
<link>https://bpm.tips/3451/how-are-users-and-groups-managed-on-cloud-pak-for-business-automation-compared-to-websphere-ldap-in-traditional-baw</link>
<description>In traditional BAW every LDAP user could log in and teams referenced LDAP groups directly. On CP4BA our LDAP is configured, but new users get &amp;quot;not authorized&amp;quot; in Workplace and Studio. What changed in user management?</description>
<guid isPermaLink="true">https://bpm.tips/3451/how-are-users-and-groups-managed-on-cloud-pak-for-business-automation-compared-to-websphere-ldap-in-traditional-baw</guid>
<pubDate>Sun, 06 Sep 2026 13:42:12 +0000</pubDate>
</item>
<item>
<title>How do I authenticate REST API calls to Business Automation Workflow on CP4BA (Zen API key, bearer token, CSRF)?</title>
<link>https://bpm.tips/3449/how-do-i-authenticate-rest-api-calls-to-business-automation-workflow-on-cp4ba-zen-api-key-bearer-token-csrf</link>
<description>On traditional BAW our integration scripts call /rest/bpm/wle/v1 with basic authentication. On CP4BA the same calls answer with a redirect to the login page or 401. What is the correct way to authenticate a technical client on the Cloud Pak?</description>
<guid isPermaLink="true">https://bpm.tips/3449/how-do-i-authenticate-rest-api-calls-to-business-automation-workflow-on-cp4ba-zen-api-key-bearer-token-csrf</guid>
<pubDate>Sun, 06 Sep 2026 13:41:51 +0000</pubDate>
</item>
</channel>
</rss>