bug: `gws auth setup` writes double-serialized client_id/client_secret into client_secret.json (causes 401 invalid_client)

Open
#947 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
rust

Research direction

Start by reproducing the issue with gws auth setup and inspect the generated ~/.config/gws/client_secret.json, focusing on how the OAuth credentials are serialized. Confirm the fix by checking that client_id and client_secret contain plain values and that a subsequent gws auth login succeeds without invalid_client.

Written by the indexing model from the issue text.

Description

gws version: 0.22.5 (installed via npm on Windows 10)

Steps to reproduce:

  1. Run gws auth setup
  2. Complete gcloud auth login when prompted
  3. Choose "Create new project"
  4. Let the wizard finish (creates OAuth client, writes ~/.config/gws/client_secret.json)
  5. Run gws auth login

Actual behavior:
The generated client_secret.json has its client_id and client_secret fields filled with the entire JSON credentials object (double-serialized as a string) instead of the plain values:

{
  "installed": {
    "client_id": "{\"installed\":{\"client_id\":\"123-abc.apps.googleusercontent.com\",...,\"client_secret\":\"REDACTED\",...}}",
    "client_secret": "{\"installed\":{...same blob...}}"
  }
}

This causes every subsequent gws auth login attempt to fail with:

error[auth]: OAuth flow failed: Server error: invalid_client: The OAuth client was not found.

The printed "Open this URL in your browser to authenticate" link also contains the malformed client_id query param, so manually fixing the URL alone does not help until the underlying file is fixed.

Workaround:
Manually edit client_secret.json and replace client_id/client_secret with the actual plain values extracted from the nested string, then gws auth login works correctly.

Expected behavior:
gws auth setup should write the plain client_id/client_secret strings, not a re-serialized copy of the whole credentials object.

Dominant language
Rust
Stars
32.3k
Forks
2k
Avg merge
16h 3m
Merged PRs (30d)
1

Getting set up

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.