AccessToken omits `iat` claim despite documentation listing it

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

Maintainers usually reply within 1 day

@jay23606 is already working on this.

Since Oct 27, 2026.

  • #984 by @jay23606 — open

Assessment

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

Research direction

The report identifies AccessToken._generate_payload() and the base Jwt.payload property as the payload-generation entry points. Read those methods and the Access Token documentation to establish whether iat should be present, then inspect related tests. Done means the maintainers clarify the expected behavior and align the SDK or documentation, with a regression test if the SDK changes.

Written by the indexing model from the issue text.

Description

type: bug
Describe the bug

In twilio-python version 9.12.0, an Access Token generated using AccessToken and SyncGrant does not contain the iat (issued-at) claim.

I inspected the generated JWT payload and the installed SDK source code. The payload contains jti, iss, sub, nbf, exp, and grants, but no iat.

However, Twilio's documentation lists iat among the claims expected in a correctly formed Access Token.

Could the maintainers clarify whether this omission is intentional, and whether the SDK or documentation should be updated for consistency?

I have not demonstrated an authentication or authorization failure. This report is intended to clarify the observed behavior rather than claim a security vulnerability.

Code snippet
import os
import json
import base64

from twilio.jwt.access_token import AccessToken
from twilio.jwt.access_token.grants import SyncGrant

account_sid = os.environ["TWILIO_ACCOUNT_SID"]
api_key = os.environ["TWILIO_API_KEY"]
api_secret = os.environ["TWILIO_API_KEY_SECRET"]
service_sid = os.environ["SYNC_SERVICE_SID"]

token = AccessToken(
    account_sid,
    api_key,
    api_secret,
    identity="bb-test-identity",
    ttl=600,
)

token.add_grant(SyncGrant(service_sid=service_sid))
jwt = token.to_jwt()

if isinstance(jwt, bytes):
    jwt = jwt.decode("utf-8")

payload_part = jwt.split(".")[1]
payload_part += "=" * (-len(payload_part) % 4)
payload = json.loads(base64.urlsafe_b64decode(payload_part))

print("Payload claim names:", sorted(payload.keys()))
print("iat present:", "iat" in payload)
Actual behavior

With twilio-python 9.12.0, the generated Access Token payload did not include iat.

The inspected source shows that AccessToken._generate_payload() adds jti and grants, while the base Jwt.payload property adds iss and exp, and conditionally adds nbf and sub. Neither method explicitly adds iat.

My local Sync tests otherwise behaved as expected: permitted reads succeeded, and unauthorized reads and writes were rejected.

Expected behavior

I expected the SDK's behavior to be consistent with the published Access Token documentation, which describes iat as the token's issue timestamp.

If iat is required, the SDK should include it in the generated payload. If it is optional, the documentation should clarify this distinction.

References:

twilio-python version

9.12.0

Python version

3.14.7

Logs or error messages

No authentication error observed. The issue was identified by inspecting the generated JWT payload and the installed SDK source code. The token payload did not contain an iat claim.

Additional context

Environment: Kali Linux under WSL, using a Python virtual environment.

The Sync service had ACLs enabled. Tests using authorized and unauthorized test identities behaved as expected.

I also inspected the installed SDK's JWT payload-generation methods and found no explicit iat claim generation in those methods.

I have not established a security impact or confirmed that Twilio rejects these tokens. I am requesting clarification about whether this is intentional SDK behavior or a documentation inconsistency.

Could the maintainers clarify the expected behavior and, if appropriate, add a regression test?

Dominant language
Python
Stars
2.1k
Forks
821
Avg merge
9h 33m
Merged PRs (30d)
3

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 twilio/twilio-python

All issues in twilio/twilio-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.