Pandey 67895d366d fix(tokenizer): require a jwt secret when the provider is jwt (#12899) ...

#### Description

- `tokenizer.Config.Validate()` now rejects an empty
`tokenizer::jwt::secret` when `tokenizer::provider` is `jwt`. An empty
secret signs and verifies tokens with an empty key, so anyone can mint a
valid token.
- Drops the startup log in `jwttokenizer` that flagged the missing
secret and carried on, config validation now fails the boot instead.

#### Additional Information

Breaking change: a deployment running `tokenizer.provider: jwt` without
`SIGNOZ_TOKENIZER_JWT_SECRET` (or the deprecated `SIGNOZ_JWT_SECRET`)
will fail to start until a secret is set. The default provider is
`opaque`, which is unaffected.

2026-09-18 04:06:28 +00:00

..

jwttokenizer

fix(tokenizer): require a jwt secret when the provider is jwt (#12899)

2026-09-18 04:06:28 +00:00

opaquetokenizer

feat(instrumentation): add OTel exception semantic convention log handler (#10665)

2026-03-22 04:06:31 +00:00

tokenizerstore/sqltokenizerstore

feat(serviceaccount): integrate service account (#10681)

2026-04-01 07:20:59 +00:00

tokenizertest

test: add mocks for tokenizer (#10081)

2026-01-22 02:04:26 +05:30

config_test.go

fix(tokenizer): require a jwt secret when the provider is jwt (#12899)

2026-09-18 04:06:28 +00:00

config.go

fix(tokenizer): require a jwt secret when the provider is jwt (#12899)

2026-09-18 04:06:28 +00:00

tokenizer.go

feat(tokenizer|sso): add tokenizer for session management and oidc sso support (#9183)

2025-10-16 18:00:38 +05:30

wrapped.go

feat(tokenizer|sso): add tokenizer for session management and oidc sso support (#9183)

2025-10-16 18:00:38 +05:30