Since the launch of the Google Tasks API many Google Apps domain administrators have asked us how to use the API with 2-legged OAuth 1.0 (2LO) for authorization. The process for using 2LO with the Tasks API is slightly different compared to using it for the Google Calendar API or the Google Contacts APIs, which makes it a little tricky if you are already accustomed to working with those. Any use of the Tasks API needs to reference a project in the APIs Console , as the Console is used to manage API quotas and other application settings (such as IP filters). The Tasks API needs to be explicitly enabled for your domain OAuth key and secret. Referencing an APIs Console Project The Tasks API needs to know which APIs Console project is sending requests to the API (so quota can be deducted, filters can be checked, etc.). To supply this information, you need to specify the API Key key https://www.googleapis.com/tasks/v1/users/username/lists?key=<API_KEY>Java client library can do this for you automatically if you specify it after initializing the Tasks service: // Initializing the Tasks API service Enabling the Tasks API for your domain OAuth key and secret Also, before your API requests will be successful, you will need to change a few things in your OAuth Consumer Key and Secret configuration. In the Manage OAuth domain key Enable this consumer key checked and the option saying Allow access to all APIs unchecked . This may sound counterintuitive, but this option will give you access to a specific set of APIs and is necessary to access the Tasks API.Setting up the domain OAuth consumer key and secret Manage third party OAuth Client access https://www.google.com/calendar/feeds/, https://www.googleapis.com/auth/tasks Using 2-Legged OAuth with Google Tasks API for Google Apps domain administrators .Nicolas Garnier profile | twitter | events
Want to weigh in on this topic? Discuss on Buzz
2 comments :
Hi Nicolas,
maybe you can help me. I followed the java examples in the linked article "Using 2-Legged OAuth with Google Tasks API for Google Apps domain administrators" and got it working.
But as soon as I do any write operation I get a "401" response. For example if I add the following to the java example
TaskList newlist = new TaskList();
newlist.setTitle("My new list!");
TaskList il = service.tasklists.insert(newlist).execute(); // -> 401
Is this a problem with my Google Apps for Business configuration or is there no real 2-legged OAuth support for google task api write access?
Best regards,
Christian
My API console doesn't have that interface, I can only generate a Client/Secret, but I don't have all thoses checkboxes.
Do we need some sort of business account ?
Post a Comment