v1.1.1

Release 1.1.1 - Improved API Key Validation for Missing Origin Header

We are pleased to announce the release of CipherKey 1.1.1, which addresses an important issue related to API key validation when the Origin header is missing. This release introduces a fallback mechanism that improves support for internal service-to-service communications and tools like curl and Grafana, which often omit the Origin header.

Features and Enhancements

Fallback for Missing Origin Header:

• Implemented a fallback mechanism in the API key validation logic to handle cases where the Origin header is not provided. In these cases, the system will now fall back to the caller’s IP address as the Origin.
• This enhancement ensures that requests made by internal services or tools that don't include an Origin header (e.g., Grafana or curl) are still validated correctly and don't result in failed requests.

Bug Fixes and Stability Improvements

• Fixed the issue where API key validation would fail in the absence of the Origin header, preventing legitimate requests from being blocked.
• Improved the handling of internal and automated requests by supporting scenarios where the Origin header is not present, thus ensuring smooth operation for internal backend-to-backend communications.

Security Considerations

• The fallback to the IP address as the Origin has been implemented in a way that maintains the integrity of the API key validation process, ensuring that security is not compromised by the use of IP as a fallback.

Thank you for your continued support and feedback. As always, your input is invaluable to us, and we look forward to bringing you more improvements in future releases.