https://github.com/davidgtonge/chrome-cordova-identity

Fork from chrome-cordova
https://github.com/davidgtonge/chrome-cordova-identity

Last synced: 9 days ago
JSON representation

Fork from chrome-cordova

• Host: GitHub
• URL: https://github.com/davidgtonge/chrome-cordova-identity
• Owner: davidgtonge
• License: bsd-3-clause
• Created: 2014-02-26T23:18:51.000Z (over 10 years ago)
• Default Branch: master
• Last Pushed: 2014-02-26T23:31:03.000Z (over 10 years ago)
• Last Synced: 2023-03-12T04:12:30.408Z (over 1 year ago)
• Language: Java
• Size: 121 KB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# chrome.identity Plugin

This plugin provides OAuth2 authentication for Android and iOS.

On Android, this plugin uses Google Play Services; on iOS, it uses InAppBrowser.

## Status

Stable on Android; alpha on iOS.

## Reference

The API reference is [here](http://developer.chrome.com/apps/identity.html); a description of how to use the API is [here](http://developer.chrome.com/apps/app_identity.html).

## Preparing Your Application

### Android

You will need to register your application in the [Google Cloud Console](https://cloud.google.com/console).  Create a project.

On the left sidebar, navigate to "APIs & Auth" > "Registered Apps".  Click the red `Register App` button.

Register your app as an "Android" app.  This requires a package name and a SHA1 fingerprint.  To obtain the fingerprint, enter the following the command in a console window:

    keytool -exportcert -alias androiddebugkey -keystore ~/.android/debug.keystore -list -v

(On Windows, replace `~` with `%USERPROFILE%`.)

You will be prompted for a password, which is `android`.

This process will yield a client id, but no action is required with it (unlike for iOS).

### iOS

For iOS, first follow **Step 1** of the instructions [here](https://developers.google.com/+/mobile/ios/getting-started#step_1_creating_the_apis_console_project).

**Note:** If you change your app's bundle identifier at any time, you will need to correspondingly update the bundle identifier in the following places:

* the [Google Cloud Console](https://cloud.google.com/console), under "APIs & Auth" > "Registered Apps", and

* your app's URL types in Xcode (located in the app's *Info* tab).

## Updating Your Manifest

Your manifest needs to be updated to include your client id and scopes. In a Chrome App, this is done in manifest.json as follows:

    "oauth2": {

      "client_id": "YOUR_IOS_CLIENT_ID",

      "scopes": [

        "SCOPE_1",

        "SCOPE_2",

        "SCOPE_3"

      ]

    },

When using this plugin outside the context of a Chrome App, this information must be provided using `chrome.runtime.setManifest`:

    chrome.runtime.setManifest({

      oauth2: {

        client_id: 'YOUR_IOS_CLIENT_ID',

        scopes: [ 'SCOPE_1', 'SCOPE_2', 'SCOPE_3' ]

      }

    });

## Playing With Google APIs

The [Google APIs Explorer](https://developers.google.com/apis-explorer/) is a useful tool for determining required scopes and testing various API use cases.