Configure OpenSocial

I have a cluster consisting of 3 servers (mail1,2,3.example.com)and one frontend server gateway.example.com). I have installed OpenSocial component at all the 4 servers and created the Credential Store and widget catalog In dns: .example.com CNAME gateway.example.com I have created an account with the following parameters: Account type: Other Account server name: https://gateway.example.com/fiesta/container https://gateway.example.com/fiesta/container Protocol: HTTP Only from location(s): * Use Domino single sign-on if available: Enabled Domino single sign-on server: gateway.example.com Allow other accounts to use this log in information: Disabled Name of linked SAML account: Advanced Allow edits to field by the end user Home Portal URL: Authentication URL: Authentication Type: DOMINO-SSO Enforce SSL: Yes Enforce trusted sites: Yes Custom message text: Add these name/value pairs to the Properties list: Allow edits to fields listed: hideinui=false PreferredUsernameField=fullname In the Desktop policy I’ve set the following: Widget Settings How to apply this setting: Inherit from parent policy: Enforce in child policies: Widget catalog server: gateway.example.com Widget catalog application name: toolbox.nsf Widget catalog categories to install: WidgetsForAll Enable Live Text: Enable Show the My Widgets panel in the sidebar: Yes Restrict the creation of widgets to specific types: Disable Restrict provider IDs for installation/execution: Disable Restrict extension point IDs for installation/execution: Disable Create and manage an action: Enable Create and manage recognizers and content types: No Enable default recognizers: Enable Send widgets using e-mail: Enable Install widgets from e-mail or other: Enable Install widgets from catalog: Enable Publish to catalog so others can browse (subject to catalog ACLS): Gadget Server URL: https://gateway.example.com/fiesta https://gateway.example.com/fiesta Gadget Cache URL: Account Links: Security Token Account Shindig In the Security policy: Add whitelist rule for proxy servlets: /xsp/proxy/BasicProxy=https://gateway.example.com;GET,POST;DomAuthSessId,LtpaToken,LtpaToken2;;* All 4 servers have the following in thier configuration: notes.ini ENABLE_EE=1 iNotes_WA_EnableEE=1 iNotes_WA_LiveText=1 iNotes_WA_Widgets=1 iNotes_WA_OpenSocial=1 iNotes_WA_Widgets_AutoUpdate_Group=iNotesUsers iNotes_WA_Widgets_AutoUpdate_Day=1 Social Edition: Locked domain suffix: -locked.example.com Domain name for unlocked gadgets and content fetching: example.com Shindig server(s) host name: gateway.example.com I’ve registerd gadgets: NotesRegistrar.registerGadgets(“test”,“test”,“https://gateway.example.com/fiesta/gadgets/oauth2callback",“/tmp/test”,"true”) Imported and sibscribed But in the notes client, at the start i receive the following message: Something Went Wrong Verify that you have a working internet connection. If this problem persists, contact your administrator. At the same time there is no mistake notifications in Notes logs
Upd.

In workspace log:

CLFAD0271W: Could not create an instance of com.ibm.xsp.extlib.bean.STUserBeanDataProvider, contributed to the extension point com.ibm.commons.Extension with type com.ibm.xsp.extlib.social.PersonDataProvider.

Subject: RE: Configure OpenSocial

Hi Alexey,

Sorry for the very delayed response to this post. Are you still seeing issues?

I’d like to clarify the roles of the different servers in your configuration. Is gateway.example.com meant to be acting as your Domino Server with Shindig? Is that where both your credential store and widget catalog reside?

I encourage you to review the deployment cookbook (http://www-10.lotus.com/ldd/dominowiki.nsf/dx/IBM_Domino_9.0_Social_Edition_OpenSocial_Deployment_Cookbook http://www-10.lotus.com/ldd/dominowiki.nsf/dx/IBM_Domino_9.0_Social_Edition_OpenSocial_Deployment_Cookbook), especially the “Understanding the Concepts” articles, to ensure that we are on the same page when working through this issue.

Best regards,
-Stanton

Subject: Forwarded to development <>

Open Social/ss