[changelog] [Announcement] Forge corrected TTL for offline user impersonation tokens

Open
#33 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
api

Research direction

Start by checking the forge-spec affected requirement rows and whether forge-sim models the offlineUserAuthToken mutation or offline user impersonation tokens for remotes. Confirm the current simulated ttl behavior, then update the relevant specification and simulation so the returned ttl reflects the remaining validity rather than a fixed 30 minutes. Done means the affected requirement rows and any applicable simulation behavior match the stated Forge semantics.

Written by the indexing model from the issue text.

Description

upstream-changelog

GUID: CHANGE-3426
pubDate: Fri, 04 Sep 2026 16:50:56 GMT
Category: Announcement

What's changing

Atlassian fixed a bug where the ttl returned for Forge Remote offline user impersonation tokens (the offlineUserAuthToken mutation) could incorrectly report 30 minutes even though the token stayed valid for up to four hours. The returned ttl now accurately reflects the token's remaining validity. Actual token lifetime is unchanged; only the reported value was wrong. Apps that hard-coded a 30-minute refresh workaround are advised to switch to trusting the returned ttl, caching tokens longer and refreshing less often.

Parity impact for forge-sim

Area: remotes / external auth (Forge Remote token simulation). If forge-sim simulates the offlineUserAuthToken mutation or any offline user impersonation token issuance for remotes, the simulated ttl should reflect the real remaining validity (up to ~4h), not a fixed 30 minutes. Apps updated per this changelog (trusting ttl for refresh scheduling) should see the same refresh cadence in forge-sim as in Forge. If forge-sim doesn't model offline impersonation tokens yet, this pins the correct semantics to use when it does.

Link: https://developer.atlassian.com/platform/forge/changelog/#CHANGE-3426

  • forge-spec: update affected requirement rows (behavior change)
Dominant language
TypeScript
Stars
5
Forks
2
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 ryanackley/forge-sim

All issues in ryanackley/forge-sim

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.