AccessToken omits `iat` claim despite documentation listing it

オープン
#983 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@jay23606 がすでに取り組んでいます。

2026年10月27日 から。

  • #984 @jay23606 による — オープン

評価

難易度
3/5
見積もり時間
1〜2日
初心者へのやさしさ
55/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
python
領域
api, backend

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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?

主要言語
Python
スター
2.1k
フォーク
821
平均マージ
9時間 33分
マージ済み PR(30日)
3

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

twilio/twilio-python のほかの issue

twilio/twilio-python の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。