Databases
StackOverflow2013
Postsdbo
POHow to use 2 legged oauth on Google Admin Directory API
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to use 2 legged oauth on Google Admin Directory API
    primarykey
    data
    text
    <p>I am trying to write code to get all user accounts in our Google Apps domain using Google Admin Directory API with 2 Legged OAuth. Unfortunately, I can hardly find any documents or sample code for directory API. I tried the code below:</p> <pre><code>AdminService adminService = new AdminService(); Google.Apis.Authentication.OAuth2LeggedAuthenticator authenticator= new Google.Apis.Authentication.OAuth2LeggedAuthenticator(mydomainName, domainConsumerSecret, adminId, mydomainName); UsersResource usrRes = new UsersResource(adminService, authenticator); UsersResource.ListRequest listReq = usrRes.List(); Google.Apis.Admin.directory_v1.Data.Users allUsers = listReq .Fetch(); foreach (Google.Apis.Admin.directory_v1.Data.User usr in allUsers.UsersValue) { ... } </code></pre> <p>But I got the 401 unauthorized error. Then I tried the low level way using the old GData Lib.</p> <pre><code>Google.GData.Client.OAuth2LeggedAuthenticator authenticator = new OAuth2LeggedAuthenticator("MyAPP", mydomainName, domainConsumerSecret,adminId, mydomainName, "HMAC-SHA1"); HttpWebRequest request = authenticator.CreateHttpWebRequest("GET", new Uri("https://www.googleapis.com/admin/directory/v1/users?domain=mydomain.com")); HttpWebResponse response = request.GetResponse() as HttpWebResponse; </code></pre> <p>the above code got the same 401 error. </p> <p>Based on the source code of Directory API, I think 2LO is supported. However, I just cannot make it work. Anyone can help to point out my problem? Thanks.</p> <p>Another question: Is the userid (xoauth_requestor_id parameter) necessary for 2LO directory API request? I know this parameter is required for other APIs when using 2LO, but not clear if it is required for the Directory and Provisioning API. </p> <p>BTW: I would like to construct the 2LO HTTP requests from scratch without using any lib, but I haven't started this yet. I need to make sure that 2LO works on the Directory API requests.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USskyfree
    1. USskyfree
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow to use 2 legged oauth on Google Admin Directory API
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO2-legged Oauth 1.0 is deprecated. Unless you have a very specific reason for using it you should be using OAuth 2.0, possibly with Service Accounts instead.
      singulars
      1. POHow to use 2 legged oauth on Google Admin Directory API
      1. USJay Lee
    2. COThanks Jay, I found the problem, the "API key" parameter is missing
      singulars
      1. POHow to use 2 legged oauth on Google Admin Directory API
      1. USskyfree
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload