Quant.Infra.Net.Pro.Web.CharleSchwab
This release focuses on financial compliance logging hardening and safer error handling.
Key improvements:
- Added centralized sensitive-data redaction for logs and user-facing error surfaces
- Stopped emitting OAuth authorization codes, token fragments, and token refresh response bodies in normal logs
- Removed account value amounts, order identifiers, and cookie storage paths from routine operational logs
- Replaced raw exception messages in API errors, redirect query strings, and Blazor error banners with safer generic messages
- Updated version history and documentation to reflect the new compliance safeguards
Result:
Reduced risk of leaking financial or credential-sensitive information through local logs, API responses, browser history, screenshots, or support captures