Repository files navigation

This repo contains Gradle plugin code for implementing Sequencing.com's OAuth2 authentication for your Android app so that your app can securely access toSequencing.com's API and app chains.

• oAuth flow is explainedhere
• Example that uses this Gradle module is locatedhere

• Gradle integration
• Authentication flow
• Resources
• Maintainers
• Contribute

You need to follow instructions below if you want to build in and use OAuth logic in your existing or new project.

• create a new Android Gradle based project (i.e. in Android Studio or Eclipse)

• add gradle dependency

  • seegradle guides
  • add dependency into build.gradle file in dependencies section. Here is dependency declaration example:

   dependencies {compile 'com.sequencing:android-oauth:1.0.22'  }

• integrate autherization functionality

  • add imports

  importcom.sequencing.androidoauth.core.OAuth2Parameters;importcom.sequencing.androidoauth.core.ISQAuthCallback;importcom.sequencing.androidoauth.core.SQUIoAuthHandler;importcom.sequencing.oauth.core.Token;

  • for authorization you need to specify your application parameters atAuthenticationParameters. Authorization plugin use custom url schema which you should define. For example:

  AuthenticationParametersparameters =newAuthenticationParameters.ConfigurationBuilder()            .withRedirectUri("[your custom url schema]/Default/Authcallback")            .withClientId("[your client id]")            .withClientSecret("[your client secret]")            .build();

  • implementISQAuthCallback.

  /** * Callback for handling success authentication * @param token token of success authentication */voidonAuthentication(Tokentoken);/** * Callback of handling failure authentication * @param e exception of failure */voidonFailedAuthentication(Exceptione);

  • create View that will serve as initial element for authentication flow. It can be a Button or an extension of View class. Do not define onClickListener for this View.
  • createSQUIoAuthHandler instance that is handling authentication process
  • register your authentication handler by invokingauthenticate method with view, callback and app configuration

  publicvoidauthenticate(ViewviewLogin,finalISQAuthCallbackauthCallback,AuthenticationParametersparameters);

Sequencing.com uses standard OAuth approach which enables applications to obtain limited access to user accounts on an HTTP service from 3rd party applications without exposing the user's password. OAuth acts as an intermediary on behalf of the end user, providing the service with an access token that authorizes specific account information to be shared.

Authentication sequence diagram

First, the user is given an authorization code link that looks like the following:

https://sequencing.com/oauth2/authorize?redirect_uri=REDIRECT_URL&response_type=code&state=STATE&client_id=CLIENT_ID&scope=SCOPES

Here is an explanation of the link components:

• https://sequencing.com/oauth2/authorize: the API authorization endpoint
• client_id=CLIENT_ID: the application's client ID (how the API identifies the application)
• redirect_uri=REDIRECT_URL: where the service redirects the user-agent after an authorization code is granted
• response_type=code: specifies that your application is requesting an authorization code grant
• scope=CODES: specifies the level of access that the application is requesting

When the user clicks the link, they must first log in to the service, to authenticate their identity (unless they are already logged in). Then they will be prompted by the service to authorize or deny the application access to their account. Here is an example authorize application prompt

If the user clicks "Authorize Application", the service redirects the user-agent to the application redirect URI, which was specified during the client registration, along with an authorization code. The redirect would look something like this (assuming the application is "php-oauth-demo.sequencing.com"):

https://php-oauth-demo.sequencing.com/index.php?code=AUTHORIZATION_CODE

The application requests an access token from the API, by passing the authorization code along with authentication details, including the client secret, to the API token endpoint. Here is an example POST request to Sequencing.com token endpoint:

https://sequencing.com/oauth2/token

Following POST parameters have to be sent

• grant_type='authorization_code'
• code=AUTHORIZATION_CODE (where AUTHORIZATION_CODE is a code acquired in a "code" parameter in the result of redirect from sequencing.com)
• redirect_uri=REDIRECT_URL (where REDIRECT_URL is the same URL as the one used in step 1)

If the authorization is valid, the API will send a JSON response containing the access token to the application.

• App chains
• File selector code
• Developer center
• Developer documentation

This repo is actively maintained bySequencing.com. Email the Sequencing.com bioinformatics team atgittaca@sequencing.com if you require any more information or just to say hola.

We encourage you to passionately fork us. If interested in updating the master branch, please send us a pull request. If the changes contribute positively, we'll let it ride.