Liferay Sync 3 now supports SSO

Company Blogs March 21, 2016 By Dennis Ju Staff

The Sync team is pleased to announce SSO support in the latest releases of Liferay Sync desktop and mobile clients. Any SSO implementation that works against Liferay Portal will work with Liferay Sync as well (SiteMinder, OpenSSO, OAM, SAML, Shibboleth, etc). Please note this feature is for Portal EE customers only.

Below are some screenshots showing the login flow using Liferay's SAML Provider (the same SSO implementation when logging into






To try out Liferay Sync in your SSO environment, please install the latest Sync Connector EE app on your Portal 6.2 EE, download the latest Liferay Sync clients, and follow the configuration steps described in the documentation.

Feel free to contact us in the comments below or directly at

OAuth and OpenSocial

Company Blogs February 9, 2011 By Dennis Ju Staff

A growing number of websites are adopting OAuth to authorize third-party applications to interact with a user's resources.  For example, back on August 31, 2010, Twitter flipped the kill-switch on Basic Auth and starting requiring all third-party Twitter applications to authenticate using OAuth.  Other sites (ie: service providers) supporting OAuth include Evernote, Google, LinkedIn, MySpace, Photobucket, Vimeo, Yahoo, among many others.

OpenSocial defines a specification that allows gadgets to leverage OAuth to access protected resources from service providers which Liferay's OpenSocial portlet has now implemented.  In this blog post, I will demonstrate how to configure OAuth for an OpenSocial gadget in Liferay.  This example will showcase a simple Twitter gadget that shows the authenticated user's tweet timeline and allows status updates.

Note: The code to support OAuth for OpenSocial gadgets is implemented in portal trunk (revision 71759). You can grab and build the latest source code from Liferay's repository to use this feature. Otherwise, you will need to wait for the 6.1 release of the portal.

Gadget XML

Before we begin configuring our OAuth gadget, let's first take a brief look at the gadget's XML structure.  You can find the full XML for the gadget here: link.

Within the ModulePrefs element, we see the following OAuth element:

  <Service name="twitter">
    <Request url="" param_location="uri-query" />
    <Access url="" param_location="uri-query" />
    <Authorization url="" />

Gadgets using OAuth should define a Service Name and its Request, Access, and Authorization URL.  These URL's are provided by the service provider (Twitter in this example: link).  See the OpenSocial wiki for more information on these parameters: link.  

Further down in the XML within the Javascript section, there's a function named fetchData().  Take note of the, callback, params) and how the parameters are constructed to fetch data using OAuth.

Note that is part of the 0.7/0.8 OpenSocial spec and has since been deprecated.  The 0.9+ spec defines a simpler, more intuitive methods in osapi.http.get/post, however it seems Twitter doesn't return the expected results when the user has not yet granted access to the gadget.  As a result, I used the deprecated methods in my Twitter gadget.  I've contacted Twitter about osapi.http support and hope to hear back soon.  More information on and osapi.http can be found here: link.

Admin Configuration

Now let's configure our gadget.  We need to define the consumer key and secret given by our service provider.

  1. Open the OpenSocial configuration page in the Control Panel.  First add the gadget via URL as you would with any other gadget. (
  2. For any OAuth enabled gadgets, you'll see a "Manage OAuth" pop-up option under "Actions".  Click on "Managed OAuth".
  3. You will see a list of all the service names defined in your XML.  To use a service, we will need to enter a consumer key and secret.  In our case, we have one service named "twitter".  Click on the link.
  4. Now we need to retrieve a consumer key and secret from our service provider (Twitter).  Go to (sign in if you haven't already) and click on "Register a new application".
  5. Fill out all necessary information.
    • For the "Callback URL", enter Liferay's default callback URL: "http://myLiferayServer/opensocial-portlet/gadgets/oauthcallback".  (replace myLiferayServer with an appropriate value. will work for demonstration sake).
    • For "Default Access Type", select "Read & Write" as we will need to write access to post status updates.  
  6. After registering, Twitter will provide you with a consumer key and secret as well as the request token URL, access token URL, and authorize URL.  Take note of the consumer key and secret.  Also note that Twitter uses the HMAC-SHA1 algorithm.

  7. Enter the "Consumer Key" and "Consumer Secret" in the OpenSocial Control Panel page.  Select "HMAC_SYMMETRIC" for the "Key Type" then click "Save".


Adding the Gadget

  1. Now we're ready to add the gadget to a page.  Go to "My Private Pages" and click on "Add" -> "More" -> "OpenSocial" and add "Twitter Gadget".
  2. Click on "Personalize this gadget" to be redirected to the service provider.
  3. Twitter will ask the end user whether your application (ie: your gadget) should be given "the ability to access and update your data on Twitter".  You can sign out and sign in with another Twitter account here.  Click "Allow".

  4. The pop-up window should close and your gadget should now show the last 20 tweets from your timeline.  

  5. You can use the gadget to tweet your new status update.  (Note: you can also change the number of tweets to display by clicking on the wrench icon on the upper right and going to "Configuration".  The screenshot below shows the last 5 tweets instead of the default 20.)

That's it!  I hope this blog entry helps you get started creating OpenSocial gadgets that require OAuth.  Feel free to leave a comment below if you have any questions.

Showing 2 results.