Bug fix for mPulse auto-app creation feature

A component in the recent Property Manager (19.3) release and mPulse auto-app creation feature had a bug. Each time a new version of a RUM-enabled property only was changed, a new mPulse app was automatically created. mPulse auto-app creation should happen only when a change to an existing property has the mPulse behavior enabled. In this release, mPulse apps were automatically created whether the property configuration version had the mPulse behavior enabled or not.

To address the issue, the component that caused the bug has been rolled back, which prevents the auto-creation of a new mPulse app when a change is made to an existing property that does not have the mPulse behavior enabled. With this rollback, new mPulse apps are automatically created only when the mPulse behavior is added to the property configuration and the API Key field is left blank.

Updates to mPulse and Real User Monitoring (RUM)

The latest Property Manager release includes the following changes for RUM customers:

• For new properties, the mPulse behavior is automatically turned on in the property configuration with a default (blank) mPulse app API key. Leaving this mPulse API key blank automatically creates a new mPulse app that corresponds to the property. After the property is active on the Akamai production network, all of your data (beacons) are directed to your mPulse app. mPulse replaces all product templates that previously had RUM as the default behavior with mPulse (with the default API key).

• If you have RUM on an existing property, and wish to use mPulse, remove the RUM behavior from the property.

• RUM and mPulse should not coexist on the same property. If you choose to use both RUM and mPulse, you need to explicitly provide an API key for the mPulse behavior. To locate the API Key of an existing mPulse app, log in to mPulse, select the mPulse app from the Home page, then click the General tab to view the API Key.

Script Management Opt-In Service Worker Updates

The Service Worker served on a particular domain only updates with the latest version of the Akamai Script Management Service Worker in either of the following two instances:

• When a new version of the Property Manager configuration associated with that domain (and with the Script Management behavior enabled) activates.
• When a new version of a Script Management policy publishes within the Script Management application.

Note: The previously released SPOF reporting feature requires that you use a minimum Boomerang version of 1.621.0 as part of mPulse data collection.

Script Management Adds Analysis Mode Support

• Added Analysis Mode Support in which a Service Worker does not install, but the information regarding the scripts served on a domain is still analyzed and displayed in the Script Management UI.  Analysis mode is set within the Script Management behavior in Property Manager. This provides customers with a “visibility” mode.
• Safety improvements to Service Worker. Service Worker acts on script requests only and does not handle any other type of request.
• Added Support for Safari Mobile.  To enable this, you must update the Property Manager behavior to install the Service Worker on Safari Mobile.
• SPOF Protection events are collected and reported in the Script Management UI. This includes the number of SPOF actions in the last month, and the first and last time the SPOF action occurred in that timeframe.

The latest update for API Gateway includes the following enhancements:

• The property activation status check is now functional.
• Endpoint versions may now be updated when any associated hostnames have been removed from property configurations but remained in use in API configurations.
• Performance improvements in backend configuration processing.
• GraphQL users may now specify a maximum query size up to 8129 bytes.
• GraphQL users may now specify a nesting depth for queries up to 100 levels.

Global Traffic Management is General Availability

Global Traffic Management (GTM) is designed to enable Internet users to access their websites or any other IP application quickly and reliably. GTM applies an Internet-centric approach to global load balancing to provide high-site availability and responsiveness to online user requests. Unlike traditional hardware-based solutions that reside within the data center, Akamai’s Global Traffic Management service is a fault-tolerant solution that makes intelligent routing decisions based on real-time data center performance health and global Internet conditions to route online user requests to the most appropriate data center using an optimized Internet route for that user at that moment. Additional capabilities include:

• Battle tested. Routes and manages traffic for some of the world’s largest distributed user audiences.

• Massive scale. Provides the scale to absorb the largest DDoS attacks targeting the DNS infrastructure.

• Roles and permissions. Provides configuration access controls to limit who can view and edit configurations.

• Total Solution. Provides capabilities such as ASN, CIDR and geographic mapping, IP version selection, load feedback, mirror failover, weighted random distribution, and policy chaining.

The latest update for API Gateway includes the following enhancements:

• Activating a registered API no longer changes the last modified date for that registered API.
• The Reset to API settings button in API Definitions is clearly separated from other elements in the UI.
• GraphQL settings are no longer visible for registered APIs with the GraphQL feature turned off.
• The UI for OAuth scopes clearly shows all APIs and resources each scope is associated with.
• The tool for comparing API versions in API Definitions includes GraphQL and OAuth scopes settings.
• When importing a Swagger file without an API name, the server URL is no longer used as a replacement for the API name in API Definitions. Instead, API Gateway returns a 400 HTTP error response indicating that an API name should be specified in the Swagger file.
• The email alerts received after activating an API are more user-friendly.
• A bug that caused failed activations of APIs for some customers has been fixed.

The latest update for API Gateway includes the following features and enhancements:

New features:

• You may now access API Dashboard in Luna Control Center to view various charts with data about your APIs. The data appears with only a five-minute delay which lets you discover and troubleshoot issues proactively. (BETA ONLY)

Enhancements:

• In the API Endpoint Definition API, you may now import and re-import API definition files by making an application/json request to ease file upload.
• You may now add descriptions to OAuth scopes that you create in API Definitions.
• You may now define and validate any JWT public and private claims. You are no longer limited to using only reserved claims in a token.
• The dialog box that appears when switching from RESTful to GraphQL caching now includes clearer messaging to ease workflow.

The latest update for API Gateway includes the following features and bug fixes. Please note that much of the work in this release are deliverables for API Gateway 1.1 beta program.

New features:

• You can now specify in API Definitions whether your API uses GraphQL to deliver structured content to clients. If so, you can configure specific caching settings for your GraphQL API. (BETA)
• You can customize selected error messages that your APIs return to clients. This includes the error message response body, HTTP status code, and headers. (BETA)

Fixed bugs:

• Key collection names must be at least 1 character in length.
• Responses for “not-null” and “type-mismatch” errors returned in the API Endpoint Definition and Key and Quota Management APIs are more descriptive and informative.
• Responses in the API Endpoint Definition and Key and Quota Management APIs provide information about missing values.

The latest update for API Gateway includes the following features and bug fixes:

New features:

• You can customize cache keys by specifying whether to use a query string in an incoming request to differentiate objects in a cache.

Fixed bugs:

• API registration form with numerous resources renders more quickly.
• The Activate button in the Activate API window is always available.
• Quota reports show the correct graph for non-existing data.
• The manual quota reset is reflected correctly in quota reports.
• When importing an API definition file, all resources can be saved after you modify one of the imported resources.
• Reimporting Swagger files no longer produces internal server errors.
• Reimporting YAML files no longer produces internal server errors.
• The daily quota reset is displayed properly in quota reports.
• More accurate error messages are returned for quota headers-related errors.
• The error message for incorrect origin hostname is more transparent.
• API error messages are consistent in capitalization.
• The new text in the key import modal now clearly states that the import operation appends keys to a collection.
• The CSV format example in the key import modal now includes the description field.