AccessToken omits `iat` claim despite documentation listing it
Los mantenedores suelen responder en 1 día
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 55/100
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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?
- Lenguaje dominante
- Python
- Estrellas
- 2.1k
- Forks
- 821
- Merge medio
- 9 h 33 min
- PR fusionados (30 d)
- 3
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de twilio/twilio-python
-
Docs: "Handling Exceptions" should mention that network errors are not `TwilioRestException`Posiblemente ocupada @henricop la tomó hace 13 días. Abierto
Dificultad 1/5 1-3 horas Aptitud para principiantes 90/100
twilio/twilio-python#986 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Clearer diagnostic when an API Key SID is passed without `account_sid`Posiblemente ocupada @saryeljaramany la tomó hace 5 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
twilio/twilio-python#985 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
TokenPagination.next_page_async() makes a sync request and fails with an async http clientPosiblemente ocupada @sebxt la tomó hace 31 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
twilio/twilio-python#976 ·
Los mantenedores suelen responder en 1 día
-
AsyncTwilioHttpClient does not JSON-serialize request bodies for application/json endpoints (sync client does) → 400 on JSON-body v2 endpointsPosiblemente ocupada @Steve0x2a la tomó hace 77 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
twilio/twilio-python#932 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
twilio/twilio-python#930 ·
Los mantenedores suelen responder en 1 día
Todos los issues de twilio/twilio-python
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
Los mantenedores suelen responder en 1 día
-
Harden tools/pr_threads.sh: pass all printed thread fields through the deterministic sanitizerAbiertoarea:cli area:security enhancement priority:medium size:small
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
RonaldHensbergen/composable-data-stack#1338 ·
Los mantenedores suelen responder en 1 día
-
area:stdlib effort:S impact:med platform:linux type:bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
Los mantenedores suelen responder en 1 día
-
automated endpoint-dead needs-curation
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
almanac-data/climate-almanac#139 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
UKGovernmentBEIS/inspect_ai#6695 · 1 comentario ·
Los mantenedores suelen responder en 1 día