What's the relationship between the scopes in the Google Cloud OAuth consent screen and the scopes requested...
There's a section in Google Cloud Console > APIs & Services > Credentials > OAuth Consent Screen that lets you edit a list of scopes:
However it seems to have zero bearing on the actual permissions that are asked for in the user prompt, which seem to only be influenced by what I actually pass in from my code when going through the OAuth flow. The list does not seem to update itself to reflect the actual scopes you ask for from your code, and it also does not limit the scopes that you can request from your code.
Is the list of scopes configured in the OAuth Consent Screen used for anything?
oauth google-api google-cloud-platform google-oauth
asked Jan 18 at 20:13
YangYang
7,9501186134
add a comment |
There's a section in Google Cloud Console > APIs & Services > Credentials > OAuth Consent Screen that lets you edit a list of scopes:
However it seems to have zero bearing on the actual permissions that are asked for in the user prompt, which seem to only be influenced by what I actually pass in from my code when going through the OAuth flow. The list does not seem to update itself to reflect the actual scopes you ask for from your code, and it also does not limit the scopes that you can request from your code.
Is the list of scopes configured in the OAuth Consent Screen used for anything?
oauth google-api google-cloud-platform google-oauth
asked Jan 18 at 20:13
YangYang
7,9501186134
I believe this is a list of all possible scopes, and then what you pass in is what the user actually agrees to. It would allow you to limit the breadth of access to each user based on what they actually use. eg: Not accessing contacts unless they enable a 'sharing' feature.
– FridayPush
Jan 18 at 20:49
@FridayPush But you can edit this list of scopes, and it does not seem to update itself to reflect the actual scopes you ask for from your code, and it does not limit the scopes that you can request from your code.
– Yang
Jan 18 at 23:13
add a comment |
There's a section in Google Cloud Console > APIs & Services > Credentials > OAuth Consent Screen that lets you edit a list of scopes:
However it seems to have zero bearing on the actual permissions that are asked for in the user prompt, which seem to only be influenced by what I actually pass in from my code when going through the OAuth flow. The list does not seem to update itself to reflect the actual scopes you ask for from your code, and it also does not limit the scopes that you can request from your code.
Is the list of scopes configured in the OAuth Consent Screen used for anything?
oauth google-api google-cloud-platform google-oauth
asked Jan 18 at 20:13
YangYang
7,9501186134
There's a section in Google Cloud Console > APIs & Services > Credentials > OAuth Consent Screen that lets you edit a list of scopes:
However it seems to have zero bearing on the actual permissions that are asked for in the user prompt, which seem to only be influenced by what I actually pass in from my code when going through the OAuth flow. The list does not seem to update itself to reflect the actual scopes you ask for from your code, and it also does not limit the scopes that you can request from your code.
Is the list of scopes configured in the OAuth Consent Screen used for anything?
oauth google-api google-cloud-platform google-oauth
oauth google-api google-cloud-platform google-oauth
asked Jan 18 at 20:13
YangYang
7,9501186134
asked Jan 18 at 20:13
YangYang
7,9501186134
edited Jan 18 at 23:13
Yang
asked Jan 18 at 20:13
YangYang
7,9501186134
asked Jan 18 at 20:13
YangYang
7,9501186134
asked Jan 18 at 20:13
YangYang
7,9501186134
7,9501186134
I believe this is a list of all possible scopes, and then what you pass in is what the user actually agrees to. It would allow you to limit the breadth of access to each user based on what they actually use. eg: Not accessing contacts unless they enable a 'sharing' feature.
– FridayPush
Jan 18 at 20:49
@FridayPush But you can edit this list of scopes, and it does not seem to update itself to reflect the actual scopes you ask for from your code, and it does not limit the scopes that you can request from your code.
– Yang
Jan 18 at 23:13
add a comment |
I believe this is a list of all possible scopes, and then what you pass in is what the user actually agrees to. It would allow you to limit the breadth of access to each user based on what they actually use. eg: Not accessing contacts unless they enable a 'sharing' feature.
– FridayPush
Jan 18 at 20:49
@FridayPush But you can edit this list of scopes, and it does not seem to update itself to reflect the actual scopes you ask for from your code, and it does not limit the scopes that you can request from your code.
– Yang
Jan 18 at 23:13
I believe this is a list of all possible scopes, and then what you pass in is what the user actually agrees to. It would allow you to limit the breadth of access to each user based on what they actually use. eg: Not accessing contacts unless they enable a 'sharing' feature.
– FridayPush
Jan 18 at 20:49
I believe this is a list of all possible scopes, and then what you pass in is what the user actually agrees to. It would allow you to limit the breadth of access to each user based on what they actually use. eg: Not accessing contacts unless they enable a 'sharing' feature.
– FridayPush
Jan 18 at 20:49
@FridayPush But you can edit this list of scopes, and it does not seem to update itself to reflect the actual scopes you ask for from your code, and it does not limit the scopes that you can request from your code.
– Yang
Jan 18 at 23:13
@FridayPush But you can edit this list of scopes, and it does not seem to update itself to reflect the actual scopes you ask for from your code, and it does not limit the scopes that you can request from your code.
– Yang
Jan 18 at 23:13
add a comment |
1 Answer
1
active
oldest
votes
In your screenshot on the right side "Scopes for Google APIs", this is a list of scopes that your application has asked for in the past. If your app requires validation, Google will use this list as part of its process to evaluate your app. For most of the items (scopes) in the list, you can click the delete icon to remove the scope from the list.
When you create your credentials (OAuth Tokens), you specify the scopes that you want at that time. The list in your screenshot is not used to specify scopes, just to keep track of the ones that you have used.
answered Jan 18 at 21:23
John HanleyJohn Hanley
15.3k2528
You can clearly add to as well as remove from the list of scopes from that UI, and it does not seem to update itself based on the scopes that I ask for from my code. And it does not restrict the scopes you can request from your code during the OAuth flow.
– Yang
Jan 18 at 23:10
@Yang - I am not sure that you are trying to say to me in your comment. The screen does update itself based upon the scopes your application uses. The update is not instantaneous. The second part of your comment is correct - as I said in my answer. The key point is that the screen is used for app approval. Add or delete any scopes that you want. Once approved however, if you use a scope not approved then the approval process needs to be repeated.
– John Hanley
Jan 18 at 23:33
add a comment |
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%2f54260827%2fwhats-the-relationship-between-the-scopes-in-the-google-cloud-oauth-consent-scr%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
In your screenshot on the right side "Scopes for Google APIs", this is a list of scopes that your application has asked for in the past. If your app requires validation, Google will use this list as part of its process to evaluate your app. For most of the items (scopes) in the list, you can click the delete icon to remove the scope from the list.
When you create your credentials (OAuth Tokens), you specify the scopes that you want at that time. The list in your screenshot is not used to specify scopes, just to keep track of the ones that you have used.
answered Jan 18 at 21:23
John HanleyJohn Hanley
15.3k2528
You can clearly add to as well as remove from the list of scopes from that UI, and it does not seem to update itself based on the scopes that I ask for from my code. And it does not restrict the scopes you can request from your code during the OAuth flow.
– Yang
Jan 18 at 23:10
@Yang - I am not sure that you are trying to say to me in your comment. The screen does update itself based upon the scopes your application uses. The update is not instantaneous. The second part of your comment is correct - as I said in my answer. The key point is that the screen is used for app approval. Add or delete any scopes that you want. Once approved however, if you use a scope not approved then the approval process needs to be repeated.
– John Hanley
Jan 18 at 23:33
add a comment |
In your screenshot on the right side "Scopes for Google APIs", this is a list of scopes that your application has asked for in the past. If your app requires validation, Google will use this list as part of its process to evaluate your app. For most of the items (scopes) in the list, you can click the delete icon to remove the scope from the list.
When you create your credentials (OAuth Tokens), you specify the scopes that you want at that time. The list in your screenshot is not used to specify scopes, just to keep track of the ones that you have used.
answered Jan 18 at 21:23
John HanleyJohn Hanley
15.3k2528
You can clearly add to as well as remove from the list of scopes from that UI, and it does not seem to update itself based on the scopes that I ask for from my code. And it does not restrict the scopes you can request from your code during the OAuth flow.
– Yang
Jan 18 at 23:10
@Yang - I am not sure that you are trying to say to me in your comment. The screen does update itself based upon the scopes your application uses. The update is not instantaneous. The second part of your comment is correct - as I said in my answer. The key point is that the screen is used for app approval. Add or delete any scopes that you want. Once approved however, if you use a scope not approved then the approval process needs to be repeated.
– John Hanley
Jan 18 at 23:33
add a comment |
In your screenshot on the right side "Scopes for Google APIs", this is a list of scopes that your application has asked for in the past. If your app requires validation, Google will use this list as part of its process to evaluate your app. For most of the items (scopes) in the list, you can click the delete icon to remove the scope from the list.
When you create your credentials (OAuth Tokens), you specify the scopes that you want at that time. The list in your screenshot is not used to specify scopes, just to keep track of the ones that you have used.
answered Jan 18 at 21:23
John HanleyJohn Hanley
15.3k2528
In your screenshot on the right side "Scopes for Google APIs", this is a list of scopes that your application has asked for in the past. If your app requires validation, Google will use this list as part of its process to evaluate your app. For most of the items (scopes) in the list, you can click the delete icon to remove the scope from the list.
When you create your credentials (OAuth Tokens), you specify the scopes that you want at that time. The list in your screenshot is not used to specify scopes, just to keep track of the ones that you have used.
answered Jan 18 at 21:23
John HanleyJohn Hanley
15.3k2528
answered Jan 18 at 21:23
John HanleyJohn Hanley
15.3k2528
answered Jan 18 at 21:23
John HanleyJohn Hanley
15.3k2528
answered Jan 18 at 21:23
John HanleyJohn Hanley
15.3k2528
15.3k2528
You can clearly add to as well as remove from the list of scopes from that UI, and it does not seem to update itself based on the scopes that I ask for from my code. And it does not restrict the scopes you can request from your code during the OAuth flow.
– Yang
Jan 18 at 23:10
@Yang - I am not sure that you are trying to say to me in your comment. The screen does update itself based upon the scopes your application uses. The update is not instantaneous. The second part of your comment is correct - as I said in my answer. The key point is that the screen is used for app approval. Add or delete any scopes that you want. Once approved however, if you use a scope not approved then the approval process needs to be repeated.
– John Hanley
Jan 18 at 23:33
add a comment |
You can clearly add to as well as remove from the list of scopes from that UI, and it does not seem to update itself based on the scopes that I ask for from my code. And it does not restrict the scopes you can request from your code during the OAuth flow.
– Yang
Jan 18 at 23:10
@Yang - I am not sure that you are trying to say to me in your comment. The screen does update itself based upon the scopes your application uses. The update is not instantaneous. The second part of your comment is correct - as I said in my answer. The key point is that the screen is used for app approval. Add or delete any scopes that you want. Once approved however, if you use a scope not approved then the approval process needs to be repeated.
– John Hanley
Jan 18 at 23:33
You can clearly add to as well as remove from the list of scopes from that UI, and it does not seem to update itself based on the scopes that I ask for from my code. And it does not restrict the scopes you can request from your code during the OAuth flow.
– Yang
Jan 18 at 23:10
You can clearly add to as well as remove from the list of scopes from that UI, and it does not seem to update itself based on the scopes that I ask for from my code. And it does not restrict the scopes you can request from your code during the OAuth flow.
– Yang
Jan 18 at 23:10
@Yang - I am not sure that you are trying to say to me in your comment. The screen does update itself based upon the scopes your application uses. The update is not instantaneous. The second part of your comment is correct - as I said in my answer. The key point is that the screen is used for app approval. Add or delete any scopes that you want. Once approved however, if you use a scope not approved then the approval process needs to be repeated.
– John Hanley
Jan 18 at 23:33
@Yang - I am not sure that you are trying to say to me in your comment. The screen does update itself based upon the scopes your application uses. The update is not instantaneous. The second part of your comment is correct - as I said in my answer. The key point is that the screen is used for app approval. Add or delete any scopes that you want. Once approved however, if you use a scope not approved then the approval process needs to be repeated.
– John Hanley
Jan 18 at 23:33
add a comment |
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%2f54260827%2fwhats-the-relationship-between-the-scopes-in-the-google-cloud-oauth-consent-scr%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
I believe this is a list of all possible scopes, and then what you pass in is what the user actually agrees to. It would allow you to limit the breadth of access to each user based on what they actually use. eg: Not accessing contacts unless they enable a 'sharing' feature.
– FridayPush
Jan 18 at 20:49
@FridayPush But you can edit this list of scopes, and it does not seem to update itself to reflect the actual scopes you ask for from your code, and it does not limit the scopes that you can request from your code.
– Yang
Jan 18 at 23:13