Known Issues
Get a brief overview of the known issues.
Topic | Description |
API Namespace creation | Currently it is only supported to create an API Namespace from scratch. The other two possibilities will be introduced in a later release and are disabled in the current version. |
Supported API Specification | The current version will only support to generate APIs based on OpenAPI 3.0. The possibility to generate SWAGGER 2.0 will be introduced in a later release. |
API Integration – IBM Business Process Manager | This feature is currently under TechPreview and classified as experimental. Currently it makes no difference wether you mark it as true or false for an API Namespace. The Toolkit will always be created. |
API Integration – IBM API Connect | The current version will not support an integration to IBM API Connect. The Feature will be introduced in a later release and is disabled in the current version. |
Solution Hub | Used WebClient (WebFlux) in the SolcProxyController logs "Only one connection receive subscriber allowed" when response status is an error. Caused by https://github.com/spring-projects/spring-framework/issues/22096 |
ca_certs | It is currently not possible to use the debugger when the Keycloak and the solution have different certificates. |
Fetching permissions | When getting new permissions or when permissions are changed in Repository Membership or in Role Mapping, it may take up to 3 minutes (MAX) for them to get activated in the case of repository membership being changed. If the Role Mappings are changed then you should log out and log in again to activate the permissions. At the moment this time period is not configurable. In order to shorten the time needed to activate the new permissions, you can clear the cache manually by calling the corresponding API, e.g. through the Swagger UI interface. |
Discriminator property for oneOf schemas | When creating a oneOf schema and setting a discriminator, a required property is created with the discriminator name and it is automatically attached to each schema that belongs in the oneOf schema. Therefore, when any of these schemas are used independently, then the discriminator property must be set accordingly to '#/components/schemas/<schema_localIdentifier>'. |
Defining the discriminator property | If any of the schemas of a oneOf schema have the a property with the same name as the discriminator name, then the property of the schema will be replaced with the discriminator. The discriminator is an enum value of type String. Therefore, make sure there are no properties in any of the schemas of a oneOf schema with the prporty name the name of the discriminator while creating a oneOf schema. |