docs: April 2026 security hardening — flags, metrics, migration notes#61
Open
lakhansamani wants to merge 1 commit intomainfrom
Open
docs: April 2026 security hardening — flags, metrics, migration notes#61lakhansamani wants to merge 1 commit intomainfrom
lakhansamani wants to merge 1 commit intomainfrom
Conversation
Adds a dedicated docs/core/security.md page covering every CLI flag
and behavioural change introduced by the April 2026 security batch
across the authorizer repo, plus targeted updates to the surrounding
docs so the new flags appear in the right reference sections.
New page (docs/core/security.md):
- TL;DR with the two breaking changes (--admin-secret required,
--trusted-proxies default empty)
- Admin authentication
- Refresh tokens (new --refresh-token-expires-in flag)
- Trusted proxies (with topology table covering single host, nginx,
Cloudflare, AWS ALB, Kubernetes)
- CORS, CSRF, and origin enforcement
- HTTP server timeouts and graceful shutdown
- Security response headers (HSTS, CSP, Permissions-Policy)
- OAuth flow hardening (response_mode=query rejection, GET /logout
confirmation page, OIDC RP-initiated logout note)
- Webhook SSRF protection (DNS rebinding TOCTOU defence)
- OTP and TOTP at rest, including the rolling-deploy note for
multi-replica clusters and the JWT key-rotation warning
- GraphQL hardening (depth/complexity/alias/body-size limits, GET
transport disabled)
- Rate limiter behaviour changes (Redis error propagation, window
math fix)
- Login error normalization and user-enumeration defences
server-config.md:
- Mark --admin-secret as required and explain the breaking change
- Document --trusted-proxies as a top-level core flag
- Add --refresh-token-expires-in to the JWT section
- Add the new --graphql-max-* limits to the GraphQL security section
- Add a new "Security headers" section covering --enable-hsts and
--disable-csp
- Add a "Full security reference" pointer to the new security page
- Renumber the trailing sections accordingly
- Add a JWT key-rotation warning that ties into TOTP at-rest
metrics-monitoring.md:
- Register the new authorizer_graphql_limit_rejections_total counter
with its limit-kind label values and tuning guidance
migration/v1-to-v2.md:
- New "Breaking changes — April 2026 security batch" subsection at
the end of section 3, covering --admin-secret and --trusted-proxies
with concrete examples for the most common reverse-proxy topologies
sidebars.ts:
- Add core/security to the Core sidebar between server-config and
databases so it surfaces in the natural reading order
✅ Deploy Preview for authorizerdev-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents every operator-visible change introduced by the April 2026 security batch in the main authorizer repo (PRs #582–#590).
What's added
Test plan