The CRE is the successor to Mashup Enabler and adds the ability to render OpenSocial gadgets as well as iWidgets. Throughout the
Connections documentation, the Connections instance of CRE will be referred to as the
This section of the documentation is specific to the administration of the Widget Container. More details on the CRE in general can be found in the
If you wish to add gadgets deployed externally, such as iGoogle gadgets, you must configure locked domains. Locking domains isolates semi-trusted gadgets and prevents them from accessing SSO tokens or via DOM access to the parent page of the gadget iFrame that can be used to forward sensitive data to external sites. For more information on locked domains, refer to
Administering gadgets for IBM Connections and widgets for Home page
You can extend the functionality of the Home page application by adding custom widgets and extend IBM
Connections by adding OpenSocial gadgets. To make the widgets and gadgets available for use, you can add them from the Administration view and then enable them for use.
Gadget registration commands
Administrators can use NewsWidgetCatalogService commands to register gadgets, particularly if the IBM
Connections Home page application, with its administrative interface, has not been installed.
Configuring OAuth for custom gadgets
Connections 4.0 release supports an OAuth 2.0 consumer proxy that allows the Homepage component to surface gadgets in an OpenSocial container that can interact with an OAuth 2.0 protected service. In order for this proxy to function, there are a series of new administration commands that are exposed in the News service to define OAuth 2.0 providers, clients, and the associated gadget that will interact with the protected service.
Configuring per-host proxy access rules for OpenSocial gadgets
Proxy access is configured on a per-gadget level. This configuration is distinct from the proxy configuration file in that it specifies which end points may be contacted rather than what tokens or headers may be sent. In general the proxy access is configured during gadget registration by setting the Server access
setting to external (outside the SSO domain) or all server access. Beyond these two settings, an administrator may expand or restrict access further by specifying custom proxy or (in cases where they wish for extra security) may enumerate per-gadget-per-server (and even per user) custom proxy rules. Custom proxy rules are defined in a separate configuration file.
Clearing the widget cache
Two methods of clearing the widget cache are available: using the IBM
Connections Home page administrative user interface or using a NewsWidgetCatalogService command.
Security token properties
You can configure security token properties in the LCC/opensocial-config.xml in the LotusConnections-config directory.