Creating a JSON document type fails if the enum keyword contains an empty array as one of its elements in JSON schema.When creating a JSON document type if JSON schema contains enum keyword with an empty array as one of its elements, then Integration Server writes a service exception to the error log.

This issue is resolved.

Integration Server does not create the URL alias automatically while creating a REST API descriptor (RAD) using resource first approach.

While creating a RAD using the resource first approach, Integration Server does not create the URL alias automatically if the basepath is updated.

This issue is now resolved.

JSON schema validation fails but error messages are not clear as to the cause.

If validation fails for the JSON schema constructs 'anyOf', 'allOf' and 'oneOf' keyword, the error messages do not clearly indicate the cause or location of the validation failure.

This issue is now resolved.

Integration Server generates invalid Swagger document after creating a provider REST API descriptor (RAD).

When user creates a provider RAD using a Swagger document that contains an inline schema in the body or in the response, then Integration Server generates an invalid Swagger document while creating the provider RAD.

This issue is resolved.

Attempting to create a JSON document type from a JSON schema that contains a cyclic reference at the property level might cause out of memory errors.

This issue is now resolved.

When deploying the JNDI configuration for ActiveMQ to Cloud, the provider URL is incorrectly changed to point to Universal Messaging.

This issue is now resolved.

Designer should not allow adding an OAuth type security definition for a REST API descriptor if the scope name added in Integration Server contains a large string. Currently Designer does not display any error while adding the security definition.

Desginer now displays the following message when the scope length is too long: The scope name, scopeName exceeds the maximum length.

Integration Server allows to access a resource with incorrect authentication type.

After assigning OAuth type security definition for a resource, Integration Server allows accessing the resource using basic authentication without any error.

This issue is resolved.

Integration Server adds incorrect output to the REST connector service while executing it.

While executing a REST connector service, if the REST API returns an undefined data in the response, then Integration Server adds that data in the connector service output.

This issue is resolved.

Integration Server throws an exception while creating a REST API descriptor (RAD) from a Swagger file containing a path defined as '/test/{id}-{name}'.

While importing a valid Swagger file to create a RAD, if the Swagger file contains a path having multiple path parameters in a single URI segment, Integration Server throws a validation error.

This issue no longer occurs.

Integration Server throws NullPointerException while calling a connector service in a consumer REST API descriptor (RAD).

If a consumer RAD is created and then renamed, an attempt to run any of the connector service, ends with a NullPointerException.

There is no workaround for this issue.

Using the Integration Server Administrator UI to set the Kerberos "Use Subject Credentials Only" property (which corresponds to the "javax.security.auth.useSubjectCredsOnly" field) on the Security > Kerberos > Kerberos Settings screen sets an incorrect property.

This issue is now resolved.

A StringIndexOutOfBoundsException occurs when the root service wm.server.apigateway:getApiData tries to fetch details of published APIs from an API Gateway instance running on a different machine.

This issue is now resolved.

Consumer endpoint aliases with Kerberos as the authentication method are not editable.

This issue is now resolved.

Command Central displays incorrect status of the OSGI-IS_{is_instanceName} component. Command Central incorrectly displays the status of the OSGI-IS_{is_instanceName} component in the Instances tab as “STARTING” even when the child nodes do not have a Platform Manager plugin Offline implementation. This issue occurs only after an Integration server restart.

This issue is now resolved.

Designer displays the erroneous input parameter 'secure' under the service signature of pub.client:restClient service.

This issue is resolved.

Composite definitions for fixed-length record parsers without delimiters do not get parsed.

This issue is resolved. Support for composite definitions for fixed-length record parsers without delimiters can now be done through flat file schema generation wizard.

In Integration Server, when the newly added "recordIdentifierPre105Version" property is set to true the record identifier will not be added to pub.flatFile:convertToString service output for composite fields.

There is no input to handle line separators other than modifying the flat file schema record delimiter based on the Operating System where Integration Server is running.

To resolve this, a new input 'lineSeparator' is added to the delimiters input document in the pub.flatFile:convertToString service to specify how handle CRLF/LF/CR line separators in the service output.