Identity and access management

Use Keycloak for identity and access management in IBM Cloud Pak® for Integration. The IBM Cloud Pak foundational services operator automatically installs Keycloak (at the correct version) when it is needed by an instance that is part of Cloud Pak for Integration. If you need to install the IBM Cloud Pak foundational services operator, see Installing the operators.

Important: API Connect cluster instances include their own system for providing identity and access management services. You can connect an API Connect cluster to Keycloak to provide identity management, or you can use it without Keycloak. You must connect an API Connect cluster to Keycloak if you want to use features such as single sign-on, Asset Repository integration, and Integrated Authoring in Integration design. In either case, IBM API Connect is used for access management.

AKS installs

When installing on Azure Kubernetes Service , IBM Cloud Pak foundational services and Keycloak are not used. Instead, users are managed locally in Kubernetes secrets. For more information, see Managing users on AKS.