-
Notifications
You must be signed in to change notification settings - Fork 0
Logging
Doug Fennell edited this page Sep 22, 2025
·
1 revision
Hybrid authentication fallback (mTLS + JWT)
-
Behavior
- If a JWT is provided but invalid, and the client certificate is valid, the system intentionally continues with certificate-only authentication.
- This is normal operation in hybrid mode and should not be treated as an error by default.
-
Log levels
- Default: Debug level message only
- Development or explicitly enabled: Warning message with request context
-
Configuration
# Default (recommended): no warnings for hybrid fallback
export NODE_ENV=production
# Enable warnings for debugging (development or explicit opt-in)
export RDCP_WARN_ON_HYBRID_FALLBACK='true'
- Message shapes
- Debug (default):
- "Hybrid auth: JWT invalid, using certificate only"
- Warn (development/explicit):
- "JWT validation failed, continuing with cert-only auth" with fields { route, method, clientId }
- Debug (default):
Notes
- Keep WARN level for actionable problems only; avoid noisy logs that cause false alarms
- Use DEBUG for expected control flow transitions such as hybrid fallback
Getting Started: Installation β’ Basic Usage β’ Authentication
Migration: From Manual Implementation β’ Framework Examples β’ Publishing Guide
Protocol: RDCP v1.0 Specification β’ Implementation Guide β’ API Reference
π Home | π¦ NPM Package | π GitHub | π Issues
RDCP SDK v1.0.0 - Runtime Debug Control Protocol implementation for JavaScript/Node.js applications
- Implementation-Status
- JavaScript-vs-TypeScript-Boundaries
- Core-Package-Boundaries
- Publishing-Setup
- Contributing
- API-Reference
- Protocol Specification
- Implementation Guide
- RDCP-Primitive-Types
- Protocol-Schemas
- Protocol-Error-Codes
- API-Reference
Version: 1.0.0
Protocol: RDCP v1.0
License: Apache-2.0