Skip to content

token expiration broken when using GCE service accounts #212

Closed
#213
Closed
token expiration broken when using GCE service accounts#212
#213
Assignees
stephenplusplus
Labels
🚨This issue needs some love.triage meI really want to be triaged.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
Milestone
Core Stable

Description

@silvolu
silvolu
opened on Sep 16, 2014

The access token expiration is computed using the value of the token_expires field of the token, but the access token returned by GCE service accounts doesn't contain such field, only expires_in.

Activity

  1. stephenplusplus
    self-assigned this
    on Sep 17, 2014
  2. stephenplusplus
    added 5 commits that reference this issue on Sep 17, 2014

    fix(connection): set token expiration date for GCE

    e44cfbd

    fix(connection): set token expiration date for GCE

    8be5e2d

    fix(connection): set token expiration date for GCE

    ec5f537

    fix(connection): set token expiration date for GCE

    9ab8488

    fix(connection): set token expiration date for GCE

    2eb9903
  3. o-klp
    added 2 commits that reference this issue on Sep 19, 2014

    fix(connection) changed token expiration calculation - issue googleap…

    6e2dbf8

    fix(connection) changed token expiration calculation - issue googleap…

    eb9c5d9

  4. o-klp commented on Sep 19, 2014

    @o-klp
    o-klp
    on Sep 19, 2014

    Fixed and issued pull request: https://github.com/GoogleCloudPlatform/gcloud-node/issues

  5. stephenplusplus
    added
    in progress
    on Sep 23, 2014
  6. silvolu
    closed this as completedin #213on Sep 23, 2014
  7. beriberikix
    removed
    in progress
    on Sep 23, 2014
  8. jgeewax
    added
    auth
    type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
    on Feb 2, 2015
  9. jgeewax
    added this to the Core Stable milestone on Feb 2, 2015

  10. 34 remaining items

  11. GautamSharda
    added a commit that references this issue on Feb 2, 2026

    chore: use unique UUID per system test (#212)

    7e421a1
  12. sofisl
    added a commit that references this issue on Feb 3, 2026

    chore(deps): update dependency sinon to v7 (#212)

    6a4b494
  13. GautamSharda
    added a commit that references this issue on Feb 3, 2026

    chore: use unique UUID per system test (#212)

    1ce33af
  14. sofisl
    added a commit that references this issue on Feb 5, 2026

    fix(deps): update dependency sinon to v7 (#212)

    e14a532
  15. GautamSharda
    added a commit that references this issue on Feb 5, 2026

    chore(deps): update dependency @types/glob to v7 (#212)

    4190413
  16. sofisl
    added a commit that references this issue on Feb 17, 2026

    fix(deps): update dependency sinon to v7 (#212)

    f050c9b
  17. GautamSharda
    added a commit that references this issue on Feb 23, 2026

    chore(deps): update dependency @types/glob to v7 (#212)

    91609df
  18. sofisl
    added a commit that references this issue on Feb 24, 2026

    fix(package): update @google-cloud/common to version 0.20.0 (#212)

    66e384a
  19. GautamSharda
    added a commit that references this issue on Feb 26, 2026

    chore(deps): update dependency @types/glob to v7 (#212)

    cc79f75
  20. sofisl
    added a commit that references this issue on Feb 26, 2026

    fixes #202 by retrying on an UNKNOWN error code (#212)

    f927793
  21. codyoss
    added a commit that references this issue on Mar 5, 2026

    docs: add links to the CHANGELOG from the README.md for Java and Node (…

    12e966a
  22. sofisl
    added a commit that references this issue on Mar 5, 2026

    docs: add instructions for authenticating for system tests (#212)

    e268fdd
  23. codyoss
    added 2 commits that reference this issue on Mar 9, 2026

    chore: release 3.0.1 (#212)

    1208f8f

    chore: release 3.0.1 (#212)

    141772f
  24. GautamSharda
    added a commit that references this issue on Mar 12, 2026

    allow ServiceObject`s parent to be an ServiceObject (#212)

    4e988a6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

🚨This issue needs some love.triage meI really want to be triaged.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions