How kanidm/webauthn-rs works
Main Components
a. Core Components:
• Webauthn-RS (Main API Layer)
• Webauthn-RS-Core (Protocol Implementation)
• Webauthn-RS-Proto (Protocol Bindings)
• FIDO-MDS (Authenticator Metadata Service)
b. External Components:
• Web Browsers/Clients
• Hardware Authenticators
• Application Servers
Component Relationships
[Client Layer]
• Web Browsers
• Hardware Authenticators (USB/NFC/Bluetooth)
[Integration Layer]
• Tutorial Implementations (Actix/Axum/Tide)
• WebAuthn-RS API
[Core Processing Layer]
• WebAuthn-RS-Core
• WebAuthn-RS-Proto
[Support Services]
• FIDO-MDS
• Device Catalog
• Attestation CA
Key Elements to Highlight
a. Authentication Flow:
• Registration path
• Authentication path
• Attestation verification flow
b. Security Boundaries:
• Client-side security context
• Server-side security context
• Hardware security boundaries
Implementation Details
a. Core Libraries:
[webauthn-rs]
• ↑
[webauthn-rs-core]
• ↑
[webauthn-rs-proto]
b. Transport Layers:
• USB (fido-hid-rs)
• NFC
• Bluetooth
• Cable tunnel server
c. Support Services:
• Device catalog
• Attestation CA
• FIDO MDS integration
Additional Notes
• Notes about security boundaries and trust relationships
• Optional components (like the compatibility tester) in a different style
• Version/compatibility information for supported authenticators
Implementation Patterns
• The modular architecture allowing different transport mechanisms
• The separation of concerns between protocol and implementation
• The security-first approach with enforced constraints
• The extensibility points for different web frameworks