In IBM Cloud Pak for Integration (CP4I) v2021.2, Foundational Services provide authentication and access control mechanisms, including Single Sign-On (SSO) integration. The two supported authentication types for SSO are:
OpenShift Authentication
IBM Cloud Pak for Integration leverages OpenShift authentication to integrate with existing identity providers.
OpenShift authentication supports OAuth-based authentication, allowing users to sign in using an OpenShift identity provider, such as LDAP, OIDC, or SAML.
This method enables seamless user access without requiring additional login credentials.
SAML authentication allows integration with enterprise identity providers (IdPs) such as IBM Security Verify, Okta, Microsoft Active Directory Federation Services (ADFS), and other SAML 2.0-compatible IdPs.
It provides federated identity management for SSO across enterprise applications, ensuring secure access to Cloud Pak services.
A. Basic Authentication – Incorrect
Basic authentication (username and password) is not used for Single Sign-On (SSO). SSO mechanisms require identity federation through OpenID Connect (OIDC) or SAML.
C. PublicKey – Incorrect
PublicKey authentication (such as SSH key-based authentication) is used for system-level access, not for SSO in Foundational Services.
E. Local User Registry – Incorrect
While local user registries can store credentials, they do not provide SSO capabilities. SSO requires federated identity providers like OpenShift authentication or SAML-based IdPs.
Why the other options are incorrect:
IBM Cloud Pak Foundational Services Authentication Guide
OpenShift Authentication and Identity Providers
IBM Cloud Pak for Integration SSO Configuration
IBM Cloud Pak for Integration (CP4I) v2021.2 Administration References:
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit