|
|
|
For federated customers using internal apps that access features in IBM Connections Cloud, a SAML 2.0 profile for the OAuth 2.0 authorization grant enables the app to access features on behalf of users. |
|
|
|
IBM Connections Cloud recommends the use of OAuth 2.0 for authenticating users with third-party applications. OAuth 2.0 removes the need to store username-password pairs, allows for granular access to data, and works in concert with SAML authentication. |
|
|
|
This article will show how to handle common issues when using OAuth |
|
|
|
IBM Connections Cloud™uses the Open Authorization (OAuth) protocol for API access. OAuth is a protocol that provides a way for company applications to interact with APIs on the behalf of users without knowing their authentication credentials. |
|
|
|
Single sign-on (SSO) allows users to use a single set of credentials to access multiple systems. For better usability and tighter integration, IBM Connections Cloud™ allows SSO capabilities for partner applications. |
|
|
|
Before using IBM SmartCloud™ SaaS Business Support System (BSS) APIs, you must set up a vendor and get authorization to call APIs. |