Skip to content

feat: Add IAM OAuth scope to appsscript.json #296

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
PierrickVoulet merged 1 commit into from
Feb 3, 2026
Merged

feat: Add IAM OAuth scope to appsscript.json #296

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions apps-script/chat/a2ui-useraction-ai-agent/appsscript.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,7 @@
"chat": {}
},
"oauthScopes": [
"https://www.googleapis.com/auth/iam",
Copy link

@gemini-code-assist gemini-code-assist bot Feb 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

security-high high

The https://www.googleapis.com/auth/iam scope grants broad permissions to view and manage all of a user's Google Cloud IAM resources. Following the principle of least privilege, such a powerful scope should only be requested when strictly necessary.

The script in Credentials.gs supports two authentication methods:

  1. Service account impersonation (which requires this iam scope).
  2. Using a service account key (which does not require this scope).

By including this scope in the manifest, all users of the add-on will be prompted to grant this powerful permission, even if their configuration uses the service account key method. This leads to an over-provisioning of permissions for those users and increases the potential security risk.

To mitigate this, consider one of the following approaches:

  • Support only one authentication method (e.g., service account impersonation) to ensure the requested scope is always required.
  • If both methods must be supported, clearly document for administrators that this permission is only needed for the impersonation flow, and explain the security implications. This allows them to make an informed decision.

"https://www.googleapis.com/auth/script.external_request"
]
}
Loading