Known Issues
This page lists all known and approved issues. If available, the future fix version for each ticket is listed in the table. If a mentioned version is released, the known issue entry will be removed from the list.
Services:
The service packages that were released in ApiOmat 20.03.0 contain an issue, that a running service (except Yambas, Dashboard and Analytics) doesn't get stopped during package update (f.i. when updating to ApiOmat 20.03.1). Therefore, you have to stop the service manually before update or uninstall. The issue is fixed in packages that are build with at least the release of ApiOmat 20.03.1.
|
Schlüssel |
Zusammenfassung |
Lösung |
|
[LDAP] Prevent bind calls against LDAP if authorization header contains a bearer token |
Unresolved |
|
|
healthcheck on readiness and liveness is not woking as expected |
Unresolved |
|
|
Unresolved |
||
|
Unresolved |
||
|
Unresolved |
||
|
Unresolved |
||
|
Bouncer Integration Tests with Dispatcher occasionally hangs |
Unresolved |
|
|
Unresolved |
||
|
Unresolved |
||
|
Unresolved |
||
|
Unresolved |
||
|
[AOM Dispatcher] dot notation leads to error if configuration is persisted in MongoDB |
Unresolved |
|
|
[AOM Dispatcher] Configured and mounted configuration is not used in version 1.9.0 |
Unresolved |
|
|
Unresolved |
||
|
[C#] AbstractClientDataModel has field AppName but should be ApplicationName |
Unresolved |
|
|
Unresolved |
||
|
null for uri on custom REST endpoint when authorization header contains no Basic keyword |
Unresolved |
|
|
Authentifizierung um Ihren Vorgang abzurufen |
||