Skip to content

Fix GCP docs accuracy: legacy tokeninfo endpoint, region placeholder, typos - #395

Open
carlospolop wants to merge 1 commit into
masterfrom
gcp-course-accuracy-2026
Open

carlospolop wants to merge 1 commit into
masterfrom
gcp-course-accuracy-2026

Conversation

@carlospolop

Copy link
Copy Markdown
Collaborator

Small accuracy fixes found while reviewing the GCP pages:

  • gcp-basic-information — use the current tokeninfo endpoint https://oauth2.googleapis.com/tokeninfo instead of the legacy https://www.googleapis.com/oauth2/v1/tokeninfo.
  • gcp-appengine-privesc — the App Engine URL region component is a region-ID placeholder (<REGION_ID>, e.g. uc for us-central), not the literal oa. Now matches the enum/unauth pages.
  • gcp-secretmanager-privesc — typo <scret-name><secret-name>.
  • gcp-kms-post-exploitation — typo asymetrictasymmetric.

4 files changed, 4 insertions(+), 4 deletions(-).

🤖 Generated with Claude Code

… typos

While reviewing the GCP pages for course accuracy, found four small errors:

- gcp-basic-information: use the current tokeninfo endpoint
  (oauth2.googleapis.com/tokeninfo) instead of the legacy
  www.googleapis.com/oauth2/v1/tokeninfo.
- app-engine-privesc: the app URL region component is a region ID
  placeholder (<REGION_ID>, e.g. `uc`), not the literal `oa`.
- secretmanager-privesc: typo `<scret-name>` -> `<secret-name>`.
- kms-post-exploitation: typo `asymetrict` -> `asymmetric`.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UFWVHSD4gybTA13BrVx7c7
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant