Skip to content

Request an explicit short lifetime when issuing a JWT - #1072

Merged
maoueh merged 1 commit into
developfrom
feature/docs--request-an-explicit-short-lifetime-when-issuing-a-jwt--substreams-
Nov 18, 2026
Merged

maoueh merged 1 commit into
developfrom
feature/docs--request-an-explicit-short-lifetime-when-issuing-a-jwt--substreams-

Conversation

@maoueh

@maoueh maoueh commented Nov 18, 2026

Copy link
Copy Markdown
Contributor
  • The "Issuing a JWT" example now sends "lifetime": 900. Without it the issuer applied its default, so copying the example produced a very long-lived token, contradicting the page's own guidance.
  • Document lifetime right after the example: requested validity in seconds, always set it, keep it short, and expires_at is the source of truth since the issuer may cap it.
  • First rule in "Rules for handling JWTs" now says to always send a short lifetime, while keeping the "read expires_at" rule.
  • No other /v1/auth/issue snippets exist in the docs. No change-log entry: the authentication page is itself still under Unreleased.

@maoueh
maoueh requested a review from joshkauffman November 18, 2026 19:40
@dfuse-bot

Copy link
Copy Markdown

🔍 Vulnerabilities of ghcr.io/streamingfast/substreams:74d6de0

📦 Image Reference ghcr.io/streamingfast/substreams:74d6de0
digestsha256:b4f5af6c8a8e8186d589fc7ba5dbb44121bf66a1ff27ad65da6b7e8b6ac87648
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
platformlinux/amd64
size98 MB
packages387
📦 Base Image ubuntu:24.04
also known as
  • noble
  • noble-20261110
digestsha256:77eb101c607d6e3d4f5ad0c8a02c2136c689b98aba1f359e6502ba517e5c57ec
vulnerabilitiescritical: 0 high: 0 medium: 20 low: 3

@maoueh
maoueh merged commit 5bb8a09 into develop Nov 18, 2026
9 checks passed
@maoueh
maoueh deleted the feature/docs--request-an-explicit-short-lifetime-when-issuing-a-jwt--substreams- branch November 18, 2026 20:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants