AccessToken omits `iat` claim despite documentation listing it
Mantenedores costumam responder em até 1 dia
Avaliação
- Dificuldade
- 3/5
- Tempo estimado
- 1-2 dias
- Facilidade para iniciantes
- 55/100
Direção de pesquisa
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.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
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?
- Linguagem predominante
- Python
- Estrelas
- 2.1k
- Forks
- 821
- Merge médio
- 9h 33min
- PRs com merge (30d)
- 3
Preparar o ambiente
- Inclui um Dockerfile ou arquivo Docker Compose
- Tem um modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de twilio/twilio-python
-
Docs: "Handling Exceptions" should mention that network errors are not `TwilioRestException`Talvez já em andamento @henricop assumiu há 13 dias. Aberta
Dificuldade 1/5 1-3 horas Facilidade para iniciantes 90/100
twilio/twilio-python#986 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
Clearer diagnostic when an API Key SID is passed without `account_sid`Talvez já em andamento @saryeljaramany assumiu há 5 dias. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 82/100
twilio/twilio-python#985 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
TokenPagination.next_page_async() makes a sync request and fails with an async http clientTalvez já em andamento @sebxt assumiu há 32 dias. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 82/100
twilio/twilio-python#976 ·
Mantenedores costumam responder em até 1 dia
-
AsyncTwilioHttpClient does not JSON-serialize request bodies for application/json endpoints (sync client does) → 400 on JSON-body v2 endpointsTalvez já em andamento @Steve0x2a assumiu há 77 dias. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 82/100
twilio/twilio-python#932 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 88/100
twilio/twilio-python#930 ·
Mantenedores costumam responder em até 1 dia
Todas as issues de twilio/twilio-python
Issues semelhantes
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 64/100
Mantenedores costumam responder em até 1 dia
-
Harden tools/pr_threads.sh: pass all printed thread fields through the deterministic sanitizerAbertaarea:cli area:security enhancement priority:medium size:small
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
RonaldHensbergen/composable-data-stack#1338 ·
Mantenedores costumam responder em até 1 dia
-
area:stdlib effort:S impact:med platform:linux type:bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 84/100
Mantenedores costumam responder em até 1 dia
-
automated endpoint-dead needs-curation
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
almanac-data/climate-almanac#139 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 82/100
UKGovernmentBEIS/inspect_ai#6695 · 1 comentário ·
Mantenedores costumam responder em até 1 dia