The following sections describe miscellaneous known issues with Edge.
Area/Summary
Known issues
Cache expire results in incorrect cachehit value
When the cachehit flow variable is used after the
LookupCache policy, due to the way debug points are dispatched for
asynchronous behavior, the LookupPolicy populates the DebugInfo object
before the call back has executed, resulting in an error.
Workaround: Repeat the process (make second call) again right
after the first call.
Setting InvalidateCache Policy
PurgeChildEntries to true does not work correctly
Setting PurgeChildEntries in the
InvalidateCache policy should purge the KeyFragment element values only but
clears the entire cache.
Workaround: Use the
KeyValueMapOperations policy
to iterate cache versioning and bypass the need for cache invalidation.
Concurrent deployment requests for a SharedFlow or API proxy
can result in an inconsistent state in the Management Server
where multiple revisions are shown as deployed.
This can happen,
for example, when concurrent runs of a CI/CD deployment pipeline
occur using different revisions. To avoid this problem, avoid
deploying API proxies or SharedFlows before the current
deployment is complete.
Workaround: Avoid concurrent API proxy or SharedFlow deployments.
API call counts shown in
Edge API Analytics might contain
duplicate data.
Edge API Analytics can sometimes contain duplicate data for API calls. In that case the counts shown for
API calls in Edge API Analytics are higher than the comparable values shown in third-party analytics tools.
The following sections describe the known issues with the Edge UI.
Area
Known issues
Can't access Edge SSO Zone Administration page from navigation bar after organization is mapped to an identity zone
When you connect an organization to an identity zone,
you can no longer access the Edge SSO Zone Administration page from
the left navigation bar by selecting Admin > SSO. As a workaround, navigate to the page directly using the following URL:
https://apigee.com/sso
Known issues with the integrated portal
The following sections describe the known issues with the integrated portal.
For example, the following features from the OpenAPI Specification 3.0 are not yet supported:
allOf properties for combining and extending schemas
Remote references
If an unsupported feature is referenced in your OpenAPI Specification, in some cases the tools will ignore the feature but still
render the API reference documentation. In other cases, an unsupported feature will cause errors that prevent the successful rendering
of the API reference documentation. In either case, you will need to modify your OpenAPI Specification to avoid use of the unsupported
feature until it is supported in a future release.
Note: Because the spec editor is less restrictive than SmartDocs when rendering API reference documentation,
you may experience different results between the tools.
When using Try this API in the portal, the Accept header is set to application/json regardless of the value set for consumes in the OpenAPI Specification.
Single logout (SLO) with the SAML identity provider is not supported for custom domains. To enable a custom domain with a SAML identity provider, leave
the Sign-out URL field blank
when you configure SAML settings.
Portal admin
Simultaneous portal updates (such as page, theme, CSS, or script edits) by multiple users is not supported at this time.
If you delete an API reference documentation page from the portal, there is no way to recreate it; you'll need to delete and re-add
the API product, and regenerate the API reference documentation.
先ごろ、サービス拒否攻撃（DoS）の脆弱性が HTTP/2 プロトコル（CVE-2023-44487）の複数の実装で発見されました（Apigee Edge for Private Cloud を含む）。この脆弱性により、Apigee API 管理機能の DoS が発生する可能性があります。詳細については、Apigee セキュリティに関する公開情報 GCP-2023-032 をご覧ください。
Edge for Private Cloud のルーターと管理サーバーのコンポーネントはインターネットに公開されているため、脆弱になる可能性があります。HTTP/2 は、Edge for Private Cloud のその他の Edge 固有のコンポーネントの管理ポートで有効になっていますが、これらのコンポーネントはインターネットに公開されていません。Cassandra や Zookeeper などの Edge 以外のコンポーネントでは、HTTP/2 は有効になっていません。Edge for Private Cloud の脆弱性に対処するには、次の手順を実施することをおすすめします。
