Known limitations and restrictions
Known limitations and restrictions exist in 10.6.0.
Known limitations
The following table lists the known limitations. When a limitation is removed, that row contains the release about when resolved.
Limitation | When resolved |
---|---|
If you cannot log in to a tenant after a secure restore operation, complete the following
steps on the landlord.
|
|
GitOps integration is unsupported in the default domain. |
|
When you create the gateway-peering cluster for API rate limits, the following restrictions
and limitations apply.
|
|
If the rate limit configuration is not enabled, the following behavior occurs.
|
|
To secure connections to an Oracle data source, the following TLS protocol versions are
supported. The default protocol version is TLSv1.2. You can override the protocol version with the
CryptoProtocolVersion configuration parameter.
To specify TLSv1.2 and TLSv1.3, specify |
|
TLSv1.3 is unsupported in the TLS client profile for the analytics endpoint. | |
Although you configured a proxy policy for the API gateway, the proxy policy does not apply to the analytics endpoint if it uses the Kafka protocol. The proxy policy is applied to the analytics endpoint only when it uses the HTTP or HTTPS protocol. |
Known limitations to the API gateway support for GraphQL exist. For this list, see GraphQL limitations.
Restrictions
The following permanent restrictions apply.
- Although the volume for the RAID array appears as a subdirectory on the local: directory, it is not a subdirectory. Therefore, GitOps integration does not operate against files that you store in the RAID array.
- FIPS cryptographic mode is no longer available. The DataPower® main task always operates in permissive mode. Even when configured in FIPS mode before an upgrade, the upgrade changes the mode to permissive.
- SSLv3 is unsupported in the TLS profiles for the API Connect gateway service.