Version 2018.4.1 known limitations

• A non-xml request body is not supported in the analytics record
• A non-json request body is not supported in the analytics record
• A multipart request body is not supported in the analytics record

- Must validate at least one schema (anyOf) (context: (root).paths./example/types.post.parameters.0.schema.properties.items, line: 0, col: 0)
- Must validate one and only one schema (oneOf) (context: (root).paths./example/types.post.parameters.0, line: 46164, col: 21)
- paths./example/types.post.parameters.0.schema.properties.items.properties.pattern Does not match format 'regex' (context: (root).paths./example/types.post.parameters.0.schema.properties.items.properties.pattern, line: 0, col: 0)

Cannot read property 'type' of null

To resolve this problem, remove any invalid OpenAPI YAML files from the startup directory, then restart the API Designer user interface.

In Catalina, for designer, if you want to use test functions inside the assembly editor for the WSDL-SOAP flow, the Invoke button is disabled. Also, you cannot generate the parameter body.

To resolve this situation, you can directly publish the WSDL-SOAP APIs to the API Manager UI. Then, use the test function inside the API Manager UI - Assembly Editor. However, when you generate the body you must remove the comments <-- ... -->, as in some cases the comments are not processed correctly.

If, in the API Designer user interface, you add a User Security policy to an API assembly, the User registry list in the policy configuration window does not contain any user registries to select from. To work around this problem, add the user registry to the policy directly on the Source tab; define the following property in the - user-security: policy configuration:

user-registry: user_registry_name

API Connect Version 4.1.8 contains a set of core updates designed to improve synchronization, and to strengthen stability and data integrity. Due to the changes, we recommend increasing the ingress time-out settings if you see 504 or 409 errors when trying to create or delete a provider organization or catalog. The increased stability also means that APIs and Products take longer to process, compared to versions prior to 2018.4.1.8.

To change ingress timeout settings, see the section Kubernetes/ingress-nginx ingress controller config.map settings in the topic Kubernetes ingress controller prerequisites.

The deletion of organizations, catalogs, or applications can fail, if they or resources inside them (like draft APIs inside provider organizations) were created with Version 2018.4.1.6 or earlier. This problem does not exist if organizations, catalogs or applications, and resources inside them were created with Version 2018.4.1.7 or later. For Version 2018.4.1.6 or earlier, internal locks can remain in place and prevent successful deletion. If you encounter this problem, please contact IBM Support and open a support ticket. IBM Support can help you to clear the locks so that the deletions complete successfully.

• The ID Name field is required, but the API definition can be saved without entering a value in the field.
• The Secret Name field is required only when the Secret Required option is selected, but the user interface indicates that the Secret Name field is required regardless. Furthermore, when the field is required, the API definition can be save without entering a value.
• If the Authenticate Client Method is set to Third party, the User Registry Name field is required, but the API definition can be saved without entering a value in this field.

• API Manager user interface: https://api_manager_ui_endpoint/manager
• Cloud Manager user interface: https://cloud_admin_ui_endpoint/admin

You can, however, assign roles when adding a member to a Space, and when adding or inviting members to a Catalog.

r7430a60641-apiconnect-cc-0.log:io.netty.util.internal.OutOfDirectMemoryError: 
failed to allocate 16921 byte(s) of direct memory (used: 67100185, max: 67108864)

catalogs:
    apic-dev:
      properties:
        runtime-url: $(TARGET_URL)
    sb:
      properties:
        runtime-url: 'http://localhost:4001

You may also follow the instructions described here https://success.docker.com/article/how-to-setup-log-rotation-post-installation to set the maximum size of the log before it is rolled (max-size) and the maximum number of log files that can be present (max-files). More information about the Docker JSON File logging driver is available here: https://docs.docker.com/config/containers/logging/json-file/.

• apic products:replace
• apic products:execute-migration-target
• apic products:migrate-subscriptions

• Use the apic products:migrate-subscriptions to migrate the subscriptions in small batches. If you are replacing a Product, repeat the apic products:replace command after migrating all the subscriptions.
• Set a migration target, by using either the apic products:set-migration-target command or the Set migration target operation on the Product in the API Manager user interface. to allow users to migrate their subscriptions individually.

• apic orgs:delete
• apic catalogs:delete
• apic catalogs:clear
• apic spaces:delete
• apic spaces:clear
• apic consumer-orgs:clear

The changing of endpoints with APICUP after they have been configured in Cloud Manager is not supported. Any such endpoint changes will not be propagated to a running deployment.

• For a backup command, such as apicup subsys exec backup:
  • Verify that the backup job is created. Enter kubectl get jobs -n <namespace> and verify that the job successful status is 1.
  • Verify that the backup pod is created. Enter kubectl get pods -n <namespace> -a and verify that the pod status is either still running or completed.
• For a restore command, such as apicup subsys exec restore:
  • Verify that the restore job is created. Enter kubectl get jobs -n <namespace> and verify that the job successful status is 1.
  • Verify that the restore pod is created. Enter kubectl get pods -n <namespace> -a and verify that the pod status is either still running or completed.

You can configure terms of use for users of the Developer Portal so that the user must accept the terms and conditions before they can register or log in. This feature does not work if the user is using OIDC.

For more information, see Forcing new users to accept terms and conditions.