Social Login with LinkedIn allows an end-user to access the service from the Splash Portal, using LinkedIn credentials.
This article is an example of configuration from the Control Panel and the related end-user experience on the Splash Portal side, showing the potential of the platform and the Social Marketing application.
Control Panel configuration
This is a step-by-step example on how to configure your Venue for the LinkedIn login.
Configuring your Venue with Social Login
In order to allow your end-users to log in with LinkedIn credentials to your Venue, you have to properly configure your Access Template. For this reason, first you need to find the Access Template associated with your Splash Portal.
You can do this by clicking the Venue button in the quick access toolbar and then finding your Venue in the list. In the short summary of the Venue name, you can read the name of the Access Template used.
So find the name of your Access Template and go to the Social Login tab. This is your basic configuration from the Social Login.
We are going to use the following configuration, where all "socials" are enabled:
Social Login validation: Send a text message / Do a call
Enable Facebook: Yes
Enable LinkedIn: Yes
Enable Twitter: Yes
Enable Google+: Yes
Enable VKontakte: Yes
In this case the configuration is set at the Tenant level.
Configuring the Social Marketing application
If the Social Marketing application is enabled on your Tenant or Venue, then you can also take advantage of advanced "social" features, such as setting an access post to be published on the end-user's profile. This is a very interesting tool that allows you to get value from your venue.
However, if you don't have the Social Marketing application installed or configured on your Tenant or Venue, then the Social Login will work with standard features.
You can find the Social Marketing application in the Control Panel, in the Marketplace section.
In our case we are going to set the application to ask the end-user, during the registration phase, to post a link on the profile.
Please open the Social Marketing application and go to the Access posts section. We are going to use the following configuration, from the Tenant level that works for Facebook, LinkedIn and Twitter:
Enable social post: Yes
User decides to post or skip: No
Limit posting to the timeline: At registration only
Social networks: Facebook, LinkedIn, Twitter
Post content: I'm connected using Cloud4Wi
Add a link: http://www.cloud4wi.com/
Upload image: (none)
In the scenario described above, we are going to login with LinkedIn credentials for the first time.
Logging in to the Splash Portal
If LinkedIn access has been enabled in the Control Panel, as we did in the "Configuring your Venue with Social Login" paragraph, then the "LinkedIn Login" button appears in the Splash Portal.
By clicking this button, it is possible to access Internet by providing LinkedIn credentials.
After this, the end-user is redirected to the LinkedIn web site, where it is required to enter access credentials for the social network in order to go ahead with the procedure.
The authentication process is performed totally outside our platform. This means that the Solution will not process or store access credentials for any social network supported by the Social Login feature.
If LinkedIn recognizes access credentials, then the end-user is able to access Internet, according to the associated Internet plan.
Anyway for the first access, the end-user needs to take necessary steps to use the service correctly.
Giving LinkedIn permissions during the first access
The Social Login feature is based on a LinkedIn application called "Cloud4Wi Social Login", that acts as an intermediate layer between LinkedIn and Cloud4Wi.
As we mentioned, the end-user submits access credentials to LinkedIn. After this, the "Cloud4Wi Social Login" application checks if data are valid or not, and communicates this information to Cloud4Wi. If data is valid, the application also communicates some end-user's personal data (such as first name, last name, gender, email address, birthday, birthplace, username etc.), that is required by Cloud4Wi for the proper creation of the end-user's account and allows posts to the LinkedIn profile.
According to LinkedIn policies, when an end-user has access for the first time, he is asked to authorize the "Cloud4Wi Social Login" application to do all these steps. If the end-user accepts this, then no further authorizations are asked in the future.
Validating a mobile phone during the first access
When configuring the Control Panel, we set the Social Login validation option to "Send a text message / Do a call". This will cause the Splash Portal to ask the end-user for his mobile phone number.
It is also possible to set Cloud4Wi to send a code to the end-user’s mobile phone and ask him to enter it into the Splash Portal (by setting Social Login validation option set to "Receive code via SMS") or simply to skip the validation step (by setting Social Login validation option set to "None").
As mentioned before, the current value of the Social Login validation option is "Send a text message / Do a call". So the end-user is asked to call or send a text message to a free number, in order to confirm the provided phone number.
After this step, the registration is complete.
As already mentioned, the end-user will not be asked in the future to validate his mobile phone number if the validation has been successfully completed.
Social Marketing features: LinkedIn posts
The authorization of the "Cloud4Wi Social Login" application and the mobile phone number validation are asked only the first time, but the Social Marketing application on the Splash Portal side is executed according to the application settings.
In our case we set Limit posting to the timeline to "At registration only": this means that the Social Marketing application asks the end-user to post content. If the end-user accepts, then he is not asked any more. Otherwise, he will be asked until he accepts.
We set User decides to post or skip to "No". In this case, if the end-user refuses to post on his timeline, then he is logged out and cannot access Internet until he logs in again.
Everything has been done, so the end-user is online.
The message was posted on the end-user's timeline.