WIP: ✨ Add cred dropdown for custom OAuth scope levels #4249
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Briefly discussed in discord - https://discord.com/channels/832547762716278804/832547763191152642/1026463938692517888
Add OAuth2 scope options so users can limit their exposure. Generally useful to limit the blast radius of n8n creds, and especially important when credential sharing becomes a thing.
In this example with Google Drive a user can choose:
Read & Write
: same as the original default. Access to create, read, modify, and delete all filesRead Only
: ability to read and list all available filesn8n Files Only
: create, read, modify, and delete all files created by n8n only