<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
<channel>
<title>IBM BAW Tips Q&amp;A - Recent questions tagged iam</title>
<link>https://bpm.tips/tag/iam</link>
<description>Powered by Question2Answer</description>
<item>
<title>How do SSO and single logout work for Workplace and Studio on CP4BA with Azure AD / Okta?</title>
<link>https://bpm.tips/3471/how-do-sso-and-single-logout-work-for-workplace-and-studio-on-cp4ba-with-azure-ad-okta</link>
<description>We want users to log in to Workplace with our corporate identity provider (Azure AD) instead of LDAP passwords. On WebSphere we used a SAML TAI. How is this configured on the Cloud Pak and what about API clients?</description>
<guid isPermaLink="true">https://bpm.tips/3471/how-do-sso-and-single-logout-work-for-workplace-and-studio-on-cp4ba-with-azure-ad-okta</guid>
<pubDate>Sun, 06 Sep 2026 13:45:34 +0000</pubDate>
</item>
<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>
</channel>
</rss>