google_assistant 0.2.0 → 1.0.0.beta

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 53efc649d01191b0cfdabc34974a52e124fa8b8d
-  data.tar.gz: 8668eb3b467923e6db3d1667e7ef1c0bfde46c22
+  metadata.gz: 995844f98cf4cf9b7781addf95ddc92a0b5cb9ae
+  data.tar.gz: 7787d278be43aa748921fd70c6597c6f35ffe96e
 SHA512:
-  metadata.gz: bf5090c145e291632812c652f89f6fb729172def0fb3449413bbff1c262dacc0e6401a7999289a8109931521630113597ace1bc9bc7a26d24eebff8a19c172fb
-  data.tar.gz: 5faf5231646608ba776b52810d9a29ccae204c418ed04821c571f5b6407aa8846db0c3ad4a1e072ae180c8958bacedd72ff4392b63929295a6c640d7993678c7
+  metadata.gz: 364d269cad36246cad439cafcdf88dc29800e171366619c280f0518162a136304505b96ff39d4da519b7bd3535b7d232b9d5ab0e7dfa322a5fbecabed42210a0
+  data.tar.gz: c4e46c8cf7ed4d1f27693ff8d5646a526bc0ab7f2fedaffffa4c7d1fed46c480bba0af57658ae327178b7107227cb43fbdb4f4fe0839aa6577dc72511787ac99

data/README.md

@@ -291,6 +291,24 @@ You can use any hosting platform.
 
 6. Use the [web simulator](https://developers.google.com/actions/tools/web-simulator) to simulate. Or better yet, if your Google Home device is logged into the same account you're using to build your action, you can say "OK Google, talk to my action" to test it out directly on your device.
 
+## Authentication
+
+You can require users to log in to your service before using your assistant. Read about it in [Google's documentation](https://developers.google.com/actions/develop/identity/oauth2-code-flow). The basic flow is this:
+
+1. User tries to talk to your assistant
+2. Google tells the user they need to sign in, which they can do via the Home app on their phone
+3. The Home app links the user to your Oauth endpoint
+4. User signs in to your app
+5. Google stores the user's Oauth access and refresh tokens
+6. For each subsequent request the user makes to your assistant, Google sends the user's access token so you can identify the user
+
+In order to set this up in your assistant, the basic instructions are as follows. Read Google's documentation for the full details.
+
+1. Implement Oauth in your application
+2. Set up an Oauth client in the [Google Developer Console](https://console.developers.google.com)
+3. In the application's `action.json` file, set up account linking according to [Google's Instructions](https://developers.google.com/actions/develop/identity/account-linking#enabling_account_linking)
+4. Use `assistant.user.access_token` to identify the user
+
 ## More information
 
 Check out Google's instructions at https://developers.google.com/actions/develop/sdk/getting-started for more detail on writing and testing a Google Assistant action.

data/lib/google_assistant/user.rb

@@ -1,10 +1,11 @@
 module GoogleAssistant
   class User
-    attr_reader :id, :profile
+    attr_reader :id, :profile, :access_token
 
     def initialize(opts)
       @id = opts["user_id"]
       @profile = opts["profile"] || {}
+      @access_token = opts["access_token"]
     end
 
     def display_name

data/lib/google_assistant/version.rb

@@ -1,3 +1,3 @@
 module GoogleAssistant
-  VERSION = "0.2.0"
+  VERSION = "1.0.0.beta"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: google_assistant
 version: !ruby/object:Gem::Version
-  version: 0.2.0
+  version: 1.0.0.beta
 platform: ruby
 authors:
 - Aaron Milam
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2017-01-21 00:00:00.000000000 Z
+date: 2017-02-24 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -94,9 +94,9 @@ required_ruby_version: !ruby/object:Gem::Requirement
       version: '0'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ">="
+  - - ">"
     - !ruby/object:Gem::Version
-      version: '0'
+      version: 1.3.1
 requirements: []
 rubyforge_project: 
 rubygems_version: 2.5.1