An organization's social portal does not exist in a vacuum. Users utilize a large number of public social networks such as Facebook, LinkedIn and Twitter. This section briefly explains the mechanisms available for interacting with third party social websites.
Social Media Publisher
Since Version 188.8.131.52, IBM WebSphere Portal Server has shipped with the Social Media Publisher (Available for version 7 of the product from Greenhouse
. The SMP, facilitates the life cycle of publishing content from an organization's portal to a third party social network. An overview of the SMP as well as details on the types of messages that can be published to which third party networks is available here
Using OpenID and OAuth, it is possible to allow end users to authenticate with third party social website credentials on your social portal. Also, Single Sign On (SSO) between your portal and a third party website is possible using Security Assertion Markup Language (SAML), provided this protocol is supported by that website. Finally, the OAuth protocol allows the end user to authorize access of their social objects (for example, list of contacts), for use in your social portal.
Details on exploiting social login capabilities, and other related considerations can be found later
in this guide.
The open nature of WebSphere Portal Server, IBM Connections, and most of the third party social networks as a function of their REST based APIs and federated identity management capabilities (supported by one or more of SAML, OpenID, OAuth) allows for the construction of social applications. These applications can be surfaced in either WebSphere Portal Server, IBM Connections or the third party site, depending on what makes the most sense for the use-case.
industry standard for sharing social context between business applications further increases interoperability between an organizations social portal and those third party web sites that support this standard.