Google Directory API call permission not enough for node client
My purpose:
Get access to organisation directory information through api calls.
Problem:
OAuth was handled by node google.auth.oauth2 client running on Firebase functions. Exact credentials and api tokens stored on firebase database and pulled when needed. When I try to make the api call like so:
import { google } from 'googleapis';
const oauth2Client = new google.auth.OAuth2(
// app credential pulled from database
CLIENT_ID,
CLIENT_SECRET,
REDIRECT_URL
);
const auth = {
// Following parameters obtained from oauth response
access_token: ACCESS_TOKEN,
refresh_token: REFRESH_TOKEN,
scope: SCOPE,
token_type: 'Bearer'
expiry_date: EXPIRY_DATE
};
oauth2Client.setCredentials(auth);
const service = google.admin({version: 'directory_v1'})._options.auth = oauth2Client;
const userList = await service.users.list({
auth: oauth2Client, //probably not needed
domain: 'example.com' //my actual domain
});
Here this users.list() call will fail saying I don't have enough permission.
Other attempts:
The 'try this api' thing in google directory Api home page works fine, api calls made by the google oauth2 playground however, does not work.
The difference seems to be a ?key=SOMETHING
parameter that the directory api tryout is adding to the http request. If the same http request is made in the playground, with the same bearer token from directory api calls, and the copy pasted key string, it will work fine. Seems that the key and the token are related to each other, (so probably generated from the token somehow?).
Help appreciated :)
firebase google-oauth2 google-directory-api
add a comment |
My purpose:
Get access to organisation directory information through api calls.
Problem:
OAuth was handled by node google.auth.oauth2 client running on Firebase functions. Exact credentials and api tokens stored on firebase database and pulled when needed. When I try to make the api call like so:
import { google } from 'googleapis';
const oauth2Client = new google.auth.OAuth2(
// app credential pulled from database
CLIENT_ID,
CLIENT_SECRET,
REDIRECT_URL
);
const auth = {
// Following parameters obtained from oauth response
access_token: ACCESS_TOKEN,
refresh_token: REFRESH_TOKEN,
scope: SCOPE,
token_type: 'Bearer'
expiry_date: EXPIRY_DATE
};
oauth2Client.setCredentials(auth);
const service = google.admin({version: 'directory_v1'})._options.auth = oauth2Client;
const userList = await service.users.list({
auth: oauth2Client, //probably not needed
domain: 'example.com' //my actual domain
});
Here this users.list() call will fail saying I don't have enough permission.
Other attempts:
The 'try this api' thing in google directory Api home page works fine, api calls made by the google oauth2 playground however, does not work.
The difference seems to be a ?key=SOMETHING
parameter that the directory api tryout is adding to the http request. If the same http request is made in the playground, with the same bearer token from directory api calls, and the copy pasted key string, it will work fine. Seems that the key and the token are related to each other, (so probably generated from the token somehow?).
Help appreciated :)
firebase google-oauth2 google-directory-api
add a comment |
My purpose:
Get access to organisation directory information through api calls.
Problem:
OAuth was handled by node google.auth.oauth2 client running on Firebase functions. Exact credentials and api tokens stored on firebase database and pulled when needed. When I try to make the api call like so:
import { google } from 'googleapis';
const oauth2Client = new google.auth.OAuth2(
// app credential pulled from database
CLIENT_ID,
CLIENT_SECRET,
REDIRECT_URL
);
const auth = {
// Following parameters obtained from oauth response
access_token: ACCESS_TOKEN,
refresh_token: REFRESH_TOKEN,
scope: SCOPE,
token_type: 'Bearer'
expiry_date: EXPIRY_DATE
};
oauth2Client.setCredentials(auth);
const service = google.admin({version: 'directory_v1'})._options.auth = oauth2Client;
const userList = await service.users.list({
auth: oauth2Client, //probably not needed
domain: 'example.com' //my actual domain
});
Here this users.list() call will fail saying I don't have enough permission.
Other attempts:
The 'try this api' thing in google directory Api home page works fine, api calls made by the google oauth2 playground however, does not work.
The difference seems to be a ?key=SOMETHING
parameter that the directory api tryout is adding to the http request. If the same http request is made in the playground, with the same bearer token from directory api calls, and the copy pasted key string, it will work fine. Seems that the key and the token are related to each other, (so probably generated from the token somehow?).
Help appreciated :)
firebase google-oauth2 google-directory-api
My purpose:
Get access to organisation directory information through api calls.
Problem:
OAuth was handled by node google.auth.oauth2 client running on Firebase functions. Exact credentials and api tokens stored on firebase database and pulled when needed. When I try to make the api call like so:
import { google } from 'googleapis';
const oauth2Client = new google.auth.OAuth2(
// app credential pulled from database
CLIENT_ID,
CLIENT_SECRET,
REDIRECT_URL
);
const auth = {
// Following parameters obtained from oauth response
access_token: ACCESS_TOKEN,
refresh_token: REFRESH_TOKEN,
scope: SCOPE,
token_type: 'Bearer'
expiry_date: EXPIRY_DATE
};
oauth2Client.setCredentials(auth);
const service = google.admin({version: 'directory_v1'})._options.auth = oauth2Client;
const userList = await service.users.list({
auth: oauth2Client, //probably not needed
domain: 'example.com' //my actual domain
});
Here this users.list() call will fail saying I don't have enough permission.
Other attempts:
The 'try this api' thing in google directory Api home page works fine, api calls made by the google oauth2 playground however, does not work.
The difference seems to be a ?key=SOMETHING
parameter that the directory api tryout is adding to the http request. If the same http request is made in the playground, with the same bearer token from directory api calls, and the copy pasted key string, it will work fine. Seems that the key and the token are related to each other, (so probably generated from the token somehow?).
Help appreciated :)
firebase google-oauth2 google-directory-api
firebase google-oauth2 google-directory-api
asked Nov 19 '18 at 15:35
Shiqi ZhaoShiqi Zhao
13
13
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53377963%2fgoogle-directory-api-call-permission-not-enough-for-node-client%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53377963%2fgoogle-directory-api-call-permission-not-enough-for-node-client%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown