v1.2.0

Release 1.2.0 - API Key System Refactor, .NET 9 Support, and Enhanced Usability

We are thrilled to announce the release of CipherKey 1.2.0, which introduces a series of important updates designed to improve the usability, flexibility, and maintainability of the API key system. This release refactors key components, upgrades to .NET 9, and enhances both the functionality and user experience of the system.

Features and Enhancements

Refactoring of IApiKey Interface:

• The IApiKey interface has been refactored into a class, now called ApiKey, making it easier to instantiate and work with. You can now directly create new instances of ApiKey (e.g., new ApiKey()), simplifying usage and improving flexibility.

FallbackPolicy Behavior Change:

• The default setting of the FallbackPolicy has been changed from true to false. This ensures that fallback behavior is not triggered by default, giving developers greater control over when it should be applied.

Schema Renaming for Clarity:

• To improve clarity and consistency, the schema name has been updated from CipherKey to ApiKey, aligning better with the purpose and functionality of the system.

.NET 9 Compatibility:

• The project has been updated to support .NET 9, ensuring compatibility with the latest features, improvements, and performance enhancements available in the new version of the .NET framework.

Documentation:

• The documentation has been included, providing clearer guidance and better resources for developers to implement and work with the API key system.

Bug Fixes and Stability Improvements:

• Along with these significant improvements, we’ve addressed various bugs and stability issues, ensuring a smoother and more reliable experience.

Thank you for your continued support. As always, we welcome your feedback and look forward to bringing you even more exciting updates in future releases!

Stay secure,
The CipherKey Team