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 Automation Workflow	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.
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.
Working with two developers on one solution	In case of conflicts, delete the `package-lock.json` of the solution and execute `fss pull`.
Helm test on the package will not work	The command helm test on the package will not work, because an necessary image was not delivered.
Spring vulnerabilities	There is a security vulnerability in spring-web-5.2.1 release.
Keycloak issue	Creating keycloak clients may set the wrong redirect-uri.
Trace logging	If Trace log level is configured logs might contain sensitive user information such as ID Token.
Missing dependencies	It may be that in case a solution was exported to the local market place on a previous, outdated version and imported again in the currect, updated version that some dependencies are missing.
Pipeline Manager API	Create Pipeline fails if no `gitUsername` is specified and if the Pipeline Manager API is used directly.
OpenShift Piplines with self-signed certificates	OpenShift Piplines is not able to clone the solution project from a git repository that is using a self-signed certificate. As workaround the http address of the git repository should be used. This needs to be configured as base url in the Admin Settings of the Solution Designer.
Unmasked Password using GitBash	By using GitBash with Windows the password during the fss setup is not masked. See also recommendation for tools to be used.
Uploaded API Spec not deleted with a Namespace	At the moment, when a Integration Namespace is deleted, it does not delete the specification files of the API Dependencies with it.
Remote repository data cache	Not all cache entries are cleaned properly up if the solution is deleted. Do not create solutions with the same name on a different git provider or inside a different repository group after deleting a solution.
Avoid blanks for the alias of a Git Provider	It is not recommended to uses blanks for the alias of a Git Provider. This causes problems during the creation of a solution and using that Git Provider.
.gitignore file gets lost while importing a Solution Template	This could lead to unexpected behavior, e. g. not using latest state of node_modules in solutions. Please see the provided manual workaround after importing a solution.

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 Automation Workflow

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.

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.

Working with two developers on one solution

In case of conflicts, delete the package-lock.json of the solution and execute fss pull.

Helm test on the package will not work

The command helm test on the package will not work, because an necessary image was not delivered.

Spring vulnerabilities

There is a security vulnerability in spring-web-5.2.1 release.

Keycloak issue

Creating keycloak clients may set the wrong redirect-uri.

Trace logging

If Trace log level is configured logs might contain sensitive user information such as ID Token.

Missing dependencies

It may be that in case a solution was exported to the local market place on a previous, outdated version and imported again in the currect, updated version that some dependencies are missing.

Pipeline Manager API

Create Pipeline fails if no gitUsername is specified and if the Pipeline Manager API is used directly.

OpenShift Piplines with self-signed certificates

OpenShift Piplines is not able to clone the solution project from a git repository that is using a self-signed certificate. As workaround the http address of the git repository should be used. This needs to be configured as base url in the Admin Settings of the Solution Designer.

Unmasked Password using GitBash

By using GitBash with Windows the password during the fss setup is not masked. See also recommendation for tools to be used.

Uploaded API Spec not deleted with a Namespace

At the moment, when a Integration Namespace is deleted, it does not delete the specification files of the API Dependencies with it.

Remote repository data cache

Not all cache entries are cleaned properly up if the solution is deleted. Do not create solutions with the same name on a different git provider or inside a different repository group after deleting a solution.

Avoid blanks for the alias of a Git Provider

It is not recommended to uses blanks for the alias of a Git Provider. This causes problems during the creation of a solution and using that Git Provider.

.gitignore file gets lost while importing a Solution Template

This could lead to unexpected behavior, e. g. not using latest state of node_modules in solutions. Please see the provided manual workaround after importing a solution.