| Update of pom.xml file | Currently the root level pom.xml file will not be updated automatically in case the Java SDK version has changed. This has to be done manually in the Git repository as described here. |
| API Namespace Creation | Currently it is only supported to create an API namespace from scratch or by uploading an API specification. The other possibility (clone) will be introduced in a later release and is disabled in the current version. |
| 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. |
| 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 "one of"-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, if any of these schemas is 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" contains a property with the same name as the discriminator name, then this property 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" having the same name as the discriminator. |
| Working with two developers on one solution | In case of conflicts, delete the package-lock.json of the solution and execute fss pull. |
| Trace Logging | If trace log level is configured, logs might contain sensitive user information such as ID Token. |
| Unmasked Password using GitBash | By using GitBash with Windows, the password during fss setup is not masked. See also recommendation for tools to be used. |
| Invalid JWT Token using Dashboard Swagger-UI | Solutions that are deployed within a previous version (before 2.3) will get an invalid JWT token using the Swagger-UI from the dashboard. After a re-deployment of the solution it is fixed. |
| GitHub Enterprise Integration | The initial commit shows wrong user data in the Git repository. |
| Local Marketplace | Local Marketplace feature is not available on fresh installation without additional manual steps. |
| Existing Bindings | Existing default or custom bindings in runtime namespaces still work but are not shown via the Configuration Management REST API. |