v1.1.0

Release 1.1.0 - Enhanced API Key Validation and .NET 8 Upgrade

We are excited to announce the release of CipherKey 1.1.0, which brings crucial improvements to the API key validation process, along with an upgrade to .NET 8. This release introduces enhanced flexibility in how API keys are handled, ensuring more accurate validation and better support for complex scenarios. Let's explore the key updates in this release:

Features and Enhancements

Improved API Key Validation:

• The validation logic has been updated to correctly handle API keys that include the owner:// prefix. This ensures that keys like owner://my_key are validated properly when using the provider type validation, preventing issues where these keys were previously not recognized correctly.

Enhanced ProvideAsync Method:

• The ProvideAsync method signature has been updated to:

Task<IApiKey?> ProvideAsync(string key, string? owner)

This change allows for more flexible handling of API keys, enabling the owner portion to be separated and used in additional validation scenarios as needed.

Upgrade to .NET 8:

• The project has been upgraded from .NET 7 to .NET 8, bringing the latest improvements in performance, security, and features to ensure that your applications remain at the cutting edge of technology.

Bug Fixes and Stability Improvements

• Corrected the handling of the owner:// prefix in API keys, ensuring accurate validation.
• Updated documentation to reflect the new ProvideAsync method and its enhanced capabilities.

Thank you for your continued support and feedback as we work to enhance the security and functionality of CipherKey. As always, your insights are invaluable to us, and we look forward to your continued partnership.

Stay secure,
The CipherKey Team