Android Linkedin SDK 1.0.0 Example

In a previous post, I have explained how to access the Linkedin API's using Scribe. But luckily Linkedin have introduced their Mobile SDK for Android recently. This will save lot of times for developers and hope in the future will have lot of functions over the SDK.

In this post I'm going to give some hints and important steps to integrate Linkedin SDK for existing linkedin integrated(Using Scribe) application. When using Scribe for OAuth authentication, linkein returned us an AccessToken and we saved that in shared preferences for future use. With the new SDK we can use the previously saved AccessToken to access linkein API's without creating new token. I have added that example in SDKIntergrationActivity.java class and it's being commented. You can refer this project and previous project in Github.(Find the below code snippet in SDKIntergrationActivity.java)

LocalSharedPreferenceStorage localSharedPreferenceStorage = LocalSharedPreferenceStorage.getInstance(context);
        Token prevToken = localSharedPreferenceStorage.getLinkedinAccessToken();
        if(prevToken != null){
            AccessToken token = AccessToken.buildAccessToken(prevToken.getToken());

            liSessionManager.init(token);
        }

There are few important points that should keep in mind while integrating new SDK.

1) Keep different keystore files for different build types. Specially authorization will fail if we use debug.keystore for release build type. It will give the below error for authentication fail.

Error={"errorMessage": "either bundle id or package name \/ hash are invalid, unknown, malformed",
"errorCode": "UNKNOWN_ERROR"}

2) Generate the KEY HASH and add the PACKAGE NAME in to https://www.linkedin.com/secure/developer > Application Details > Android Package Names and Hashes. The format of the content as below and one application can support multiple packages and different build types. Each PACKAGE NAME and KEY HASH should start in a new line.

PACKAGE_NAME_ONE,KEY_HASH_ONE
PACKAGE_NAME_TWO,KEY_HASH_TWO
PACKAGE_NAME_THREE,KEY_HASH_THREE

Linkedin SDK is currently using the volley library for network operations. I have faced a limitation with volley implementation, where I tried to get User Connections list and it returned me SSL handshake exception. Find more info in here.

javax.net.ssl.SSLHandshakeException: javax.net.ssl.SSLProtocolException: SSL handshake aborted: ssl=0x6304aff0: Failure in SSL library, usually a protocol error
    error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure (external/openssl/ssl/s23_clnt.c:741 0x5e0c9fec:0x00000000)

To Overcome this exception I had to customize the volley library, by setting the setSSLSocketFactory in HttpsURLConnection class. You can find the changes in com.android.volley.toolbox.Volley class line 72.

I have uploaded source to Github.

Comments

Unknown said…
This comment has been removed by the author.
April 20, 2015 at 5:30 AM
Unknown said…
While we are generating signed apk in android studio it's giving .jks file not .keystore file.please tell me the step how to generate .keystore file and how to configure this in build.gradle.


allprojects {
repositories {
mavenCentral()
}
}

apply plugin: 'com.android.application'

android {
compileSdkVersion 22
buildToolsVersion "21.1.2"

defaultConfig {
applicationId "com.myapp.hello"
minSdkVersion 14
targetSdkVersion 22
versionCode 1
versionName "1.0"
}

signingConfigs {
sdkTest {
storeFile file("secureln.jks")
storePassword "password"
keyAlias "secureln"
keyPassword "password"
}

release {
storeFile file("secureln.jks")
storePassword "password"
keyAlias "secureln"
keyPassword "password"
}
}
buildTypes {
sdkTest {
debuggable false
signingConfig signingConfigs.sdkTest
}
release {
debuggable false
signingConfig signingConfigs.release
}
}
}

dependencies {
compile fileTree(dir: 'libs', include: ['*.jar', '*.aar'])
compile project(':linkedin-sdk')
}

configurations {
}

dependencies {
compile 'com.android.support:appcompat-v7:22.0.0'
compile 'com.google.code.gson:gson:2.3.1'
}


my gradle file look like this.and i pasted the .jks file inside app direction
April 21, 2015 at 6:52 AM
Unknown said…
But still installing signed apk its not running giving the error as you mentioned.but it working fine when installing the app in debugging mode
April 21, 2015 at 6:56 AM
Dulan Dissanayake said…
Hi Anoop Please follow this url to create .keystore file using java keytool command
http://developer.android.com/tools/publishing/app-signing.html#signing-manually

In your build.gradle file for signingConfigs use storeFile file("secureln.keystore") instead of storeFile file("secureln.jks")

Read this for more info
http://developer.android.com/tools/publishing/app-signing.html#release-mode

If you got any questions just ask.
April 27, 2015 at 10:28 PM
Dulan Dissanayake said…
Anoop : What is the error you are getting??
Is it SSL error or "UNKNOWN_ERROR"??
April 27, 2015 at 10:30 PM
sssss said…
While using sample with linkedin sdk, can you specify where client id and secret of our app is used.
May 18, 2015 at 11:30 PM
Unknown said…
I downloaded your source and running in Android studio .
I added Package_name and Hash_value in the url but ,still i am getting below error

Error={
"errorCode": "INVALID_REQUEST",
"errorMessage": "the request scope is invalid, unknown, malformed"
}
January 6, 2016 at 12:55 AM
Post a Comment

Popular posts from this blog

SSL Pinning in Android

Image
In this post I would like to explain how to do the SSL Pinnig from  Android. First of all we will get a little idea about what is SSL and Pinnig means. In this post I did referred the OWASP( Open Web Application Security Project )  page, where we can gain knowledge in common security risks of our software. Mostly in client-server communication, we uses TCP/IP protocol. Based on TCP/IP there are application layer protocols, which are well known to the world(Such as HTTP, SMTP, FTP etc...) Widely used client-server communication protocol is HTTP. HTTP is an unsecured protocol and any one can interfere the communication between clients-server. Well know security risk in HTTP is Man-In-The-Middle attack, where attacker can read/update data inside  a HTTP request/response. To overcome this kinds of attack HTTPS protocol is used, which will create a secure channel for client-server communication(This uses a X509 Certificate provided by Certificate Authority[CA] and asymmetric cryptography
Read more

Java Unit testing using JUnit @RunWith(Suite.class)

As developers we should start writing unit test cases, to be sure the unit of codes we have written works fine. Along with unit testing we can write functional test cases to be ensure our functionality works as expected. In this blog post i'm planing to explain how i used JUnit and selenium for an external OAuth login module. In my module I needed to support set of external account from different OAuth providers, such as google, facebook, microsoft etc ... This module is responsible for provide a valid access token for different provider from an API exposed to external systems. There are 3 steps in this module Add External Account. Get Tokens. Delete External Accounts. I wanted my unit and functional testing to run in the above mentioned sequence. So I used JUnit  Suit API , which executed my test classes in given sequence. To order the test methods I used  FixMethodOrder API  (This is available from JUnit 4.11). I used gradle as the build system. I'm using 3 classes
Read more

Android Event Bus Implementations using Otto

As android developers we face difficulties on decoupling different parts in android application. To overcome this difficulties, the Square has introduced an event bus for android called Otto . In this post I will demonstrate how to use Otto event bus with IntentServices in Restful android client. This code can be more optimized. This publish-subscribe style can be used to decouple many other components except the Services. This is just a sample implementation to demonstrate Event Bus concept with IntentService, except ResultReceiver usage with Services. This is more interesting when it comes to event bus. Because the same results set will be available to multiple components by publishing it on event bus. The required component should subscribe to receive the results. This is more robust than the traditional java event listners and will provide more flexibility. We can initiate the Bus object according to the requirement of our application. It is not required to be singleton or a
Read more