When a CloudStreams connection referenced by a CloudStreams connector listener explicitly references a proxy configuration, or when a default proxy configuration is available in Integration Server Administrator > Settings > Proxy Servers, and the configured proxy server throws a Basic Authentication challenge to the CloudStreams connector listener, the listener fails to enable.

This issue is resolved.

If a user adds a custom header while updating the subscription details for a connector listener, CloudStreams Server ignores it and does not send it in the request.

This issue is resolved.

Errors occur while applying OAuth v1.0a alias configurations from a source system to a target system. Because of the errors, OAuth aliases are not listed on the target system, which includes the newly created OAuth aliases. This is because update to the Access Token Secret of the respective OAuth aliases fails on the target system.

This issue is resolved.

When a provider is selected in the Integration Server Administrator, CloudStreams page, the provider label text for the selected provider is not visible.

This issue is resolved.

The "Notify Meta Channel Events" configuration option is available for a CloudStreams connector listener with the connection type defined as “Bayeux HTTP Long Polling” in the Integration Server Administrator, irrespective of whether the “Logging Invocation” action is configured. However, meta channel events are logged in the server log only if the “Logging Invocation” action is configured.

This issue is resolved.

If a connector listener is enabled and the user deletes the actionable service from the Service Development perspective in Software AG Designer, CloudStreams does not notify that the actionable service is not available.

This issue is resolved.

Subscription errors for connector listeners with "Bayeux HTTP Long Polling" connection type do not appear on the CloudStreams Administration page if the subscription has failed and the listener is enabled. The errors may be due to connection related issues, wrong subscriber configurations such as invalid or missing PushTopic name, missing or insufficient access permissions, or exceeding the concurrent user limit for the user or organization.

This issue is resolved.

"Enable Debug" option does not work for CloudStreams Streaming configuration.

Enabling the "Enable Debug" option for the CloudStreams Streaming configuration does not log additional connectivity-related information in the server logs. This is because after upgrading the cometD client library adoption, the "Enable Debug" option can no longer be supported.

This issue is resolved.