|Status:||Closed||Start date:||Jan 21, 2016|
|Priority:||Urgent||Due date:||Mar 31, 2016|
|Assignee:||Michalis Nikolopoulos||% Done:|
|Sprint:||Liferay migration to 6.2 Version|
Provide a social login portlet for liferay
The portlet should offer different ways to login based on the active login hooks (facebook, linkedin) and also a normal (username / password) login.
#10 Updated by Massimiliano Assante over 3 years ago
- Priority changed from Normal to High
- Status changed from New to In Progress
@firstname.lastname@example.org can you provide us with the link to the Google login hook? In order to test it for the moment the war and instructions would be sufficient, later (ma not so later) we would need the following:
- Google login hook ETICS configuration (you should create a new component under the portal subsystem)
- Google login hook artifact deployed on gCube Nexus Maven repository
#11 Updated by Michalis Nikolopoulos over 3 years ago
Hi, Here is the link to the war http://maven.research-infrastructures.eu/nexus/service/local/repositories/gcube-snapshots/content/gr/cite/google/Google-login-hook/1.0.0-SNAPSHOT/Google-login-hook-1.0.0-20160315.165359-3.war , all you need to do is provide google client id and google client secret either at the portal.properties file or after you have deployed the war(it won't work without the credentials), you login as administrator, navigate to control panel, then configuration in the right sidebar you click on the authentication, finally you click on the Google tab and you fill up the inputs with the credentials from google. Any feedback would be appreciated.
#13 Updated by George Kakaletris over 3 years ago
My two cents here: @email@example.com, the other adapters you have been implementing are also operational, so why don't we check also eduroam, through which we would immediately get certified accounts for a large number of researchers. Also f/b, live, twitter and other login options could be offered to BB. Any implication with those ?
#15 Updated by Panagiota Koltsida over 3 years ago
@firstname.lastname@example.org and @email@example.com the plan is to release and make available all the available adapters. We start with google and will continue with Shibboleth (required for eduroam), facebook, live, twitter and yahoo.
The social login portlet (the ticket is about) will be the portlet that will offer an attractive and "standard" UI for logging in with any of the available options (together with the standard username/password one). The login hooks can be already deployed but it is up to the portal's administrator if they will be enabled or not
#17 Updated by Massimiliano Assante over 3 years ago
The Google Login hook was integrated successfully on the Liferay 6.2 Dev Instance @CNR
#19 Updated by Panagiota Koltsida over 3 years ago
@firstname.lastname@example.org as we have already discussed it is feasible to provide a solution where a user can have multiple email addresses. In the login process we can check all user's email addresses and identify him.
This means that a user can use any of the available login options, such as google, facebook, linkedin or his credentials and always be the same user as soon as the email address has been added and validated before the first login with the corresponding email address
If you are interesting in providing this solution we can work and release the needed hooks.
#21 Updated by Panagiota Koltsida about 3 years ago
@email@example.com What we support is based on email addresses and not at social accounts. This means that if you are already registered with your email address and you use the same in a social network then you are the same user for liferay.
Regarding the portlet you are mentioning I prefer not to duplicate work since liferay provides already the UI to add additional email addresses. This is done using the "My Account" page. If you don't like this approach, you can add a section in the profile portlet where users can add additional emails. Again I'm highlighting the fact that we are talking about e-mails instead of social networks.
#22 Updated by Michalis Nikolopoulos about 3 years ago
- % Done changed from 30 to 70
Here it is the custom login hook http://maven.research-infrastructures.eu/nexus/service/local/repositories/gcube-snapshots/content/gr/cite/login/login-hook/1.0.0-SNAPSHOT/login-hook-1.0.0-20160330.151734-2.war, i would suggest reading portal.properties before deploying it. It will make clear how to use it along with the social login hooks. Any questions/feedback/suggestions will help improve it.
#23 Updated by Massimiliano Assante about 3 years ago
- File IMG_2706.jpg added
The Social login portlet was correctly deployed on the development portal at http://dev4.d4science.org:8080
Minor graphical issues should be fixed, such as the Sign In button width that does not resize correctly when on phone (see screenshot attached) and i would suggest to separate the Sign In with Google, LinkedIn etc buttons as they are sticked together.
Also, the Social login portlet should remove the default mail domain from email input textbox leaving it empty.
#27 Updated by Massimiliano Assante almost 3 years ago
- Priority changed from High to Urgent
I Just realised we'd need a minor edit when the login portlet is in "Logged in" Mode.
As in iMarine/BlueBridge production when the user access the portal page where the Sign in portlet is besides "You are signed in as $UserFull Name." we would like to add the following
Go to $CurrentSiteName Home
Go to $CurrentSite Shared Workspace
You can get $CurrentSiteName from themeDisplay.getSiteGroupName() object
The link for the shared Workspace instead you can use the following snippet:
<%@ page import="org.gcube.common.portal.GCubePortalConstants" %> <%@ page import="org.gcube.common.portal.PortalContext" %> PortalContext context = PortalContext.getConfiguration(); String mySiteURL = context.getSiteLandingPagePath(request); String lilktoworkspace = mySiteURL+ GCubePortalConstants.USER_WORKSPACE_FRIENDLY_URL;
#29 Updated by Michalis Nikolopoulos almost 3 years ago
- Assignee changed from Michalis Nikolopoulos to Massimiliano Assante
Hi @firstname.lastname@example.org i have made the changes that you requested on the login hook, you can see tha war here: http://maven.research-infrastructures.eu/nexus/service/local/repositories/gcube-snapshots/content/gr/cite/login/login-hook/1.0.0-SNAPSHOT/login-hook-1.0.0-20160719.143156-24.war.
let me know if everything is working as you expected.