AccessToken omits `iat` claim despite documentation listing it
维护者通常 1 天内回复
评估
调研方向
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 内容生成。
描述
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 分钟
- 30 天内合并 PR
- 3
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
twilio/twilio-python 的其他 Issue
-
Docs: "Handling Exceptions" should mention that network errors are not `TwilioRestException`可能已有人在做 @henricop 于 13 天前认领。 未关闭
难度 1/5 1-3 小时 新手友好度 90/100
twilio/twilio-python#986 · 1 条评论 ·
维护者通常 1 天内回复
-
Clearer diagnostic when an API Key SID is passed without `account_sid`可能已有人在做 @saryeljaramany 于 5 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
twilio/twilio-python#985 · 1 条评论 ·
维护者通常 1 天内回复
-
TokenPagination.next_page_async() makes a sync request and fails with an async http client可能已有人在做 @sebxt 于 31 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
twilio/twilio-python#976 ·
维护者通常 1 天内回复
-
AsyncTwilioHttpClient does not JSON-serialize request bodies for application/json endpoints (sync client does) → 400 on JSON-body v2 endpoints可能已有人在做 @Steve0x2a 于 77 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
twilio/twilio-python#932 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 88/100
twilio/twilio-python#930 ·
维护者通常 1 天内回复
查看 twilio/twilio-python 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 64/100
维护者通常 1 天内回复
-
area:cli area:security enhancement priority:medium size:small
难度 2/5 1-3 小时 新手友好度 76/100
RonaldHensbergen/composable-data-stack#1338 ·
维护者通常 1 天内回复
-
area:stdlib effort:S impact:med platform:linux type:bug
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
automated endpoint-dead needs-curation
难度 2/5 1-3 小时 新手友好度 76/100
almanac-data/climate-almanac#139 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
UKGovernmentBEIS/inspect_ai#6695 · 1 条评论 ·
维护者通常 1 天内回复