ProAuth 2.1.19

This release focuses on deployment flexibility and observability granularity, providing deeper control over Ingress configuration and OpenTelemetry (OTEL) data ingestion.

Infrastructure

Ingress Compatibility Infrastructure

The Ingress pathType is now fully configurable via the Helm chart (ingress.pathType). By default, it has been updated from ImplementationSpecific to Prefix to ensure broader compatibility with modern Kubernetes Ingress controllers like NGINX, Traefik, and AGIC. (#2850)

INFO

For environments requiring specific regex matching or legacy behavior, the pathType can be reverted to ImplementationSpecific via values.yaml.

Dapr PubSub Flexibility Infrastructure

Introduced dapr.nameDbDeploymentWorkerPubSub, allowing administrators to specify the exact PubSub component used by the database deployment worker. This is particularly useful in multi-tenant environments or clusters where multiple Redis/Dapr components coexist. (#2851)

Observability

Granular OTLP Endpoints Observability

ProAuth now supports per-signal OTLP endpoints. You can now route Traces, Metrics, and Logs to distinct destinations by configuring OtlpTracesExporter, OtlpMetricsExporter, and OtlpLogsExporter. (#2849)

• Traces: Exported via OtlpTracesExporter.
• Metrics: Exported via OtlpMetricsExporter.
• Logs: Exported via OtlpLogsExporter.
• Fallback: If specific signal endpoints are not defined, the global OtlpExporter settings remain in effect.

Platform Stability

Security & Dependency Maintenance

Updated internal components—including NuGet packages, .NET SDK, and container base images—to the latest patch versions. These updates address underlying security advisories and maintain the highest standard of platform reliability. (#2852)