added

API: Connectivity Suite API

With the V1.2 release of the Developer Hub, the new 1NCE Connectivity Suite API was added to the API Explorer Reference. The Connectivity Suite API allows 1NCE customers to control and query the main features of the Suite via API. For more information see the API Explorer and the Connectivity Suite section.

improved

API: New API Explorer UI

With a general small redesign of the Developer Hub, the new API Explorer was introduced. The new API integration offers a more compact and easier to use interface for testing the features of the 1NCE API. Known API Explorer features have been improved and extended. There is no change to the behavior of the actual API, all changes are only cosmetic.

improved

API: Rate Limit Adjustment

To better suite the application cases of 1NCE customers and at the same time protect the 1NCE API backend, the API rate limits have been adjusted. The set values have been determined through analyzing the current behavior of API usage. Based on the analyzed data, the newly adapted rate limits should not impact any current customer API request integration.

improved

API: New Infrastructure

1NCE is continuously growing. With more customers on our network, securing continued stability is mandatory. As of October 25, 2021, changes to the 1NCE API and server backend were introduced to increase the overall performance and security of the Management API. These changes include the DNS record for api.1nce.com and additions to the general API behavior.

deprecated

OpenVPN: Deprecated Client Configuration

The existing OpenVPN configuration file that was available thought the 1NCE Portal was deprecated due to changes brought up by OpenVPN v2.5 and above. Existing configuration files with OpenVPN versions prior to v2.5 will remain working. There is no immediate action to change existing configuration files.

added

OpenVPN: New Client Configuration

The changes brought up by OpenVPN v2.5 and above, required an adaption to the 1NCE VPN Service client configuration. Through the 1NCE Portal, only the new configuration files are available. The changed files are fully backward compatible and existing configuration files with OpenVPN versions prior to v2.5 will remain working.

improved

Data Streamer: AWS Integrations

The documentation of the AWS Integration setup for both AWS S3 and AWS Kinesis was reworked with a more step by step guide. This describes the process of using the Cloud Formation Template to create an integration with the 1NCE Data Streamer Service in more detail.

added

Data Streamer: Version 2.0

1NCE introduces Version 2.0 of the Data Streamer Service. All new streams created will behave according to the documented Version 2.0 behavior regarding Event and Usage Record format. Existing V1 data streams were migrated will continue to operate with the same functionality as before. 1NCE recommends to recreate Version 1.0 streams at some point in the near future as only Version 2.0 will receive updates and new features.

improved

Management API: Documentation

The overall documentation of the 1NCE Management API was reworked and a few bugs and inaccuracies were fixed in the update. These changes were only to the documentation of the API, the functionality was not altered.

improved

Data Streamer: REST API Integration

With the new Version 2.0 Data Streamer, the default behavior of the REST API integration has changed. In Version 1.0 two options REST API and REST API Bulk were available. With the migration to Version 2.0, the only the REST API Bulk integration is available. Newly created streams will no longer receive single HTTP POST requests for each individual record. Event and Usage records will be provided as a list of JSON objects. The default maximum amount of records in a single HTTP POST request is 3000 items.