- 21 Nov 2024
- 1 Minute to read
- Print
- PDF
October 2024 Release
- Updated on 21 Nov 2024
- 1 Minute to read
- Print
- PDF
Highlights
- Client Request Access Rule
- API Key-Based Authentication
- SSO Support Enhancements
- New Log Shipping Field
Client Request Access Rule
Self-service UI and API users require the ability to deny content according to header information.
The new Client Request Access Rule enables header access control, with the ability to reject client requests based on header information. This capability offers more robust capabilities than referrer URL blocking or user agent blocking.
As part of this rule, several new enhancements have also been made to customer-defined Media Delivery and Site Delivery URL redirects. These include the following:
- Support for MEL matching capabilities.
- Support for 301, 302, and 307 redirect HTTP status codes.
- Support for target URLs.
- Support for building target URLs with MEL.
- Configurability via both the UI and API.
API Key-Based Authentication
In addition to token-based authentication, Qwilt CDN APIs now support API key-based authentication as well.
API keys allow you to authenticate requests without using your user credentials. An API key can grant either viewer (read-only) or editor (read-and-write) permissions, and is valid for up to 365 days.
You can add or edit API keys through the Content Provider Administration menu in the UI.
SSO Support Enhancements
New SSO support enables additional authentication options when logging in to QC Services. This can be done with your Microsoft or Google credentials, if your organization has implemented SSO with Microsoft Entra and/or Google Workplace.
Logging in with either option allows you to be redirected to log in with one of these services, where you can use your own account for authentication.
New Log Shipping Field
A new log shipping MDL field has been added: SSL-Cipher. This field defines the selected Secure Sockets Layer (SSL) cipher suite.
The instructions for cipher suites detail how to secure networks through SSL.
For additional information about any of the above features or resolved issues, contact support@qwilt.com.