Release v2.53.0

Summary

AuthProxy now emits OpenTelemetry traces and metrics under the Cratis.AuthProxy scope. Export is off until you set the standard OTEL_* variables, such as OTEL_EXPORTER_OTLP_ENDPOINT.

Added

• Traces for sign-in notification, identity resolution, tenant resolution, invite exchange and bearer token validation, plus metrics for sign-ins, identity denials, identity cache requests, bearer validations, invite exchanges and upstream errors. Spans and metrics carry only low-cardinality outcome values, never tokens, claim values, subjects or tenant ids. W3C trace context is forwarded to backends. (#152)
• A telemetry page in the configuration documentation, including the exported names and how to send telemetry to Azure Monitor or Application Insights. (#152)

Changed

• Incoming baggage and Correlation-Context headers are no longer forwarded to backends. (#152)
• When telemetry export is on, request URLs are redacted before export: query strings are never recorded, invitation paths are recorded as /invite/{token}, and tenant-bearing host and URL attributes are dropped from spans and HTTP client metrics. Log scopes and framework request logs are not exported. (#152)