Note
We're happy to announce the latest update of Portway. This release focuses on authentication performance, telemetry reliability, and UI consistency. Backup your application folder before upgrading and follow the migration steps below.
Fixes in v1.5.3:
- Optimized Authentication Flow:
- Implemented
TokenVerificationCacheusing SHA-256 keying and a 30-second TTL to reduce database overhead. - Updated
TokenServiceto utilize centralized caching for all verification methods. - Added a composite index
IX_AuthTokens_ActiveFilteron (RevokedAt,ExpiresAt) for faster token lookups. - Eliminated redundant verification calls within middleware components.
- Implemented
- Enhanced Middleware Performance:
- Optimized
RateLimitingMiddlewarewith static JSON options and improved timer cleanup logic.
- Optimized
- Telemetry and Test Stability:
- Ensured
PortwayMetricsare registered unconditionally for consistent monitoring. - Resolved test failures in authentication and telemetry suites by updating mocks and assertions to match the current architecture.
- Ensured
- UI Improvements:
- Adjusted the drawer position to ensure it sits flush below the promobar.
- Maintenance:
- Removed the deprecated
tokengeneratortool. - Registered
ITokenVerificationCacheas a singleton withinAuthServiceExtensions.
- Removed the deprecated
New features in v1.5.3:
- Support for Model Context Protocol (MCP) – Expose your endpoints natively or just chat without leaving Portway
- Standardized Response Types – Introduced
PortwayResponse.csandPortwayResultsfor consistent API responses. - OpenTelemetry Instrumentation – Added telemetry for monitoring performance and errors.
- Improved Concurrency – Enhanced thread safety and resource management.
- Refactored DI – Simplified service registration with extension methods.
- Schema Standardization – Updated schemas for webhooks and file endpoints.
Migration guide
As 1.5.0 has introduced breaking changes, please follow the following steps for a safe upgrade path:
- Update Docker configurations. If you are running Portway in a container, please check the updated documentation regarding the ASP.NET port mappings, as these have changed.
- Configure Web UI access. If you plan to access the admin console externally, ensure you explicitly enable external traffic routing in your (
appsettings.json) settings. - Verify your File & Webhook endpoints. The structure of these have changed slightly,
Check our documentation for guidance. If you encounter issues, open a new Issue.
Full Changelog: v1.5.2...v1.5.3