Known Issues (4.0)

In Usage Engine 4.0, there are the following known issues:

Enhanced Security is not Enabled by Default

The property controlling if Enhanced Security is enabled or not, mz.security.user.control.enabled is not enabled by default and has to be manually added to the values.yaml file, see .

mzcli Commands Do Not Provide Return Codes

If you are using scripted solutions requiring return codes, you must use the mzsh commands, since the mzcli commands do not provide return codes.

OpenAPI Validation Error for Type enum

There is a bug when performing OpenAPI validation for parameters of the enum type. The bug is based on: https://bitbucket.org/atlassian/swagger-request-validator/issues/161/mockmvc-openapi-30-type-of-enum-parameter

The error is recorded as:

[Path ‘/requesterPlmn’] Instance type (string) does not match any allowed primitive type (allowed: [“object”])

This occurs when you send a request to an NRF server that is configured using our HTTP2 Server agent with OpenAPI validation enabled. You will be meet with a Bad Request error (Error 400) and the validation fails. There was an issue with the specifications for the type enum within the 'anyOf' section as seen from the example below.

Example: NFType found in TS29510_Nnrf_NFManagement.yaml

NFType: description: NF types known to NRF anyOf: - type: string enum: - NRF - UDM - AMF - SMF - AUSF - NEF - PCF - SMSF - NSSF - UDR - LMF - GMLC - 5G_EIR - SEPP - UPF - N3IWF - AF - UDSF - BSF - CHF - NWDAF - PCSCF - CBCF - HSS - UCMF - SOR_AF - SPAF - MME - SCSAS - SCEF - SCP - type: string



A workaround would be to add the 'type: string' parameter on the same level as the 'anyOf'.

SAP CC Notification Agent TLS Feature Not Working

The fields in SAP CC Notification Agent Configuration for configuring TLS connection are, Enable Secured Connection, Keystore Path and Keystore Password. These fields should not be enabled and used for now as it will cause the agent to fail to connect to the SAP CC server.

OpenAPI Validation Error for Unsupported Optional Parameters in HTTP2 Client

The JSON object/array is not supported in the url-encoded format in OpenAPI Validator library. This causes the access token request sent with such optional fields to be rejected by the OpenAPI validator.

The validation error is prompted as follows:

Error during request validation: [Path ‘/requesterPlmn’] Instance type (string) does not match any allowed primitive type (allowed: [“object”])

Workflows Can Only Be Viewed When Creating ECDs

When creating EC Deployments, it is no longer possible to directly edit the workflows that you add to the EC Deployment.

Open API Incorrectly Validates Request Body

Users are encountering an issue with request body validation when using a schema file that includes discriminator and oneOf keywords in the same schema object. This issue arises due to a limitation in the library implementation.

There is an existing ticket logged on this issue, see https://bitbucket.org/atlassian/swagger-request-validator/issues/771/discriminator-is-not-working-with-oneof. To work around this issue, you can disable request validation for requests containing the schema object.

Data Hub Workflow Aborts With “NoClassDefFoundError”

Users might encounter a “NoClassDefFoundError” in Data Hub Forwarding agent in Usage Engine 4.0. This is caused by an unintentional removal of a library dependency. To resolve this, the change will be reverted in the subsequent minor release of Usage Engine 4.0.