Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Missing admin reports scopes in picker

Open Beginner friendly
#765 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
88/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
rust

Research direction

Start in auth_commands.rs and inspect the static SCOPE_ENTRIES list used by gws auth login. Compare its entries with the scopes required by the built-in admin-reports service, then run the interactive picker and the provided admin-reports activities list command to verify both scopes are selectable and usable.

Written by the indexing model from the issue text.

Description

Environment:

  • CLI Version: 0.22.5 installed via homebrew
  • OS: macOS
  • Auth method: OAuth desktop app

Description:

The interactive scope picker shown by gws auth login does not include the scopes required for the admin-reports service.

The missing scopes are:

https://www.googleapis.com/auth/admin.reports.audit.readonly
https://www.googleapis.com/auth/admin.reports.usage.readonly

These are missing from the static SCOPE_ENTRIES list in auth_commands.rs.

Steps to reproduce:

  1. Run:
gws auth login
  1. Inspect the interactive scope picker.
  2. There is no visible Admin Reports audit/usage option.
  3. Run:
gws admin-reports activities list \
  --params '{"userKey":"all","applicationName":"login","maxResults":1}'

Observed:

The scope needed by admin-reports activities list cannot be selected from the interactive picker.

Expected:

The interactive picker should include the scopes needed by the built-in admin-reports service.

Suggested fix:

Add these scopes to SCOPE_ENTRIES:

https://www.googleapis.com/auth/admin.reports.audit.readonly
https://www.googleapis.com/auth/admin.reports.usage.readonly
Dominant language
Rust
Stars
31.1k
Forks
1.8k
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from googleworkspace/cli

All issues in googleworkspace/cli

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.