This is a sample Google Chrome extension that demonstrates using the Chrome Identity API to authorize access to use the Google Apps Script Execution API. If you are not familiar with these services here:
Extensions allow you to add functionality to Chrome without diving deeply into native code. You can create new extensions for Chrome with those core technologies that you're already familiar with from web development: HTML, CSS, and JavaScript.
If you have developed applications using the Execution API with HTML/JavaScript you've probably used Google client library to do this. As Google states "while not strictly necessary, can greatly assist in handling OAuth for the application". In the case of Chrome Extensions the use of client libraries can be problematic. For example, when developing my first Chrome Extension I encountered a number of errors similar to:
Refused to load the script 'https://apis.google.com/js/client.js' because it violates the following Content Security Policy directive: "script-src 'self' chrome-extension-resource:"
There are solutions for these on Stack Overflow (like this one), but I struggled to get those to work. As the Execution API relies on the user having a Google Account using the Chrome Identity API appears to be a better solution.
The quick and easy to get the code running on your computer.
- Download the source code.
- Load the extension in developer mode.
- Open the Execution API Example popup
- Authenticate extension and the Call Execution API
When the popup is opened the extension silently checks/requests a authentication token. If a token is present the authenticate button is disabled, otherwise the button is enabled and when clicked starts the interactive authentication flow.
For notes on setup and usage read this blog post
This project is based on: