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

[Auth]: Features to remove for V2

Open
#9,675 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Active
Tech stack
php

Research direction

Start by reviewing the implementations and usages of getLastReceivedToken, tokenCallback, IAM, IamTrait, FetchAuthTokenCache, and the listed interfaces. Trace how $httpHandler, token validation, and credential metadata currently flow before deciding which V2 removals or consolidations are feasible. Done means the agreed V2 design is implemented consistently and covered by the relevant tests.

Written by the indexing model from the issue text.

Description

This is a list of items we want to change / remove in the next major release

  • Remove all instances of getLastReceivedToken
  • Remove all instances of tokenCallback
  • The constructor of IAM should not contain $httpHandler - this should be passed in at runtime
  • Consider removing IAM in favor of using IamTrait in the credentials which use it.
  • Remove FetchAuthTokenCache in favor of CacheTrait
  • Consider adding $headers as second argument to FetchAuthTokenIterface::fetchAuthToken, or consolidate everything to use updateMetadata
  • Consider consolidating FetchAuthTokenInterface, UpdateMetadataInterface, ProjectIdProviderInterface, GetQuotaProjectInterface, and GetUniverseDomainInterface into a CredentialInterface.
  • Consider removing HttpClientCache, as $httpHandler can already be passed in everywhere
  • Remove Guzzle6HttpHandler
  • Remove IAMCredentials
  • Move to Firebase JWT for token validation (https://github.com/googleapis/google-auth-library-php/pull/554)
Dominant language
PHP
Stars
1.2k
Forks
464
Avg merge
2d 2h
Merged PRs (30d)
103

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 googleapis/google-cloud-php

All issues in googleapis/google-cloud-php

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.