مشکلات شناخته شده با Apigee

هنگامی که متغیر جریان cachehit بعد از خط مشی LookupCache استفاده می شود، به دلیل نحوه ارسال نقاط اشکال زدایی برای رفتار ناهمزمان، LookupPolicy شی DebugInfo را قبل از اجرای تماس مجدد پر می کند، که منجر به خطا می شود.

راه حل: بلافاصله پس از اولین تماس، فرآیند را تکرار کنید (تماس دوم را برقرار کنید).

تنظیم PurgeChildEntries در خط مشی InvalidateCache باید فقط مقادیر عنصر KeyFragment را پاک کند اما کل حافظه پنهان را پاک می کند.

راه حل: از خط مشی KeyValueMapOperations برای تکرار نسخه کش و دور زدن نیاز به باطل کردن حافظه پنهان استفاده کنید.

برای مثال، زمانی که اجرای همزمان یک خط لوله استقرار CI/CD با استفاده از تجدید نظرهای مختلف انجام می شود، ممکن است اتفاق بیفتد. برای جلوگیری از این مشکل، از استقرار پراکسی های API یا SharedFlows قبل از تکمیل استقرار فعلی خودداری کنید.

راه حل: از استقرار پروکسی API یا SharedFlow همزمان خودداری کنید.

Edge API Analytics گاهی اوقات می‌تواند حاوی داده‌های تکراری برای تماس‌های API باشد. در آن صورت، تعداد نشان داده شده برای تماس های API در Edge API Analytics بیشتر از مقادیر قابل مقایسه نشان داده شده در ابزارهای تجزیه و تحلیل شخص ثالث است.

راه حل: داده های تجزیه و تحلیل را صادر کنید و از فیلد gateway_flow_id برای حذف داده ها استفاده کنید.

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.

Workaround: Navigate to the page directly using the following URL: https://apigee.com/sso

The options TLS_DISABLED_ALGO and TLS_ENABLED_CIPHERS do not function correctly.

Workaround: Follow the steps below to enable specific ciphers for the Edge UI:

1. Open the /opt/apigee/etc/edge-ui.d/SSL.sh config file.
2. Add the property -Djdk.tls.server.cipherSuites with a comma-separated list of cipher suites in IANA notation inside the UI_OPTIONS. For example:

   UI_OPTIONS=" -Dhttp.port=disabled -Dhttps.port=9433 -Dhttps.keyStoreType=JKS -Dhttps.keyStore=/opt/apigee/customer/conf/keystore.jks -Dplay.http.sslengineprovider=services.CustomSSLEngineProvider -Dhttps.keyStorePasswordEncrypted=mypass -Djdk.tls.server.cipherSuites=TLS_RSA_WITH_AES_256_CBC_SHA256,TLS_RSA_WITH_AES_256_GCM_SHA384"

3. Save your changes to the config file.
4. Restart the Edge UI:

   /opt/apigee/apigee-service/bin/apigee-service edge-ui restart

• Apigee Edge supports OpenAPI Specification 3.0 when you create specifications using the spec editor and publish APIs using SmartDocs on your portal, though a subset of features are not yet supported.

  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.
• 138438484: Multiple servers are not supported.

• 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.
• When configuring the content security policy, it may take up to 15 minutes for changes to fully apply.
• When customizing your portal theme, it may take up to 5 minutes for changes to fully apply.

• Search will be integrated into the integrated portal in a future release.

A vulnerability (CVE-2026-42945) was disclosed affecting the ngx_http_rewrite_module in NGINX. Security scanning tools may flag the NGINX binaries included with Apigee Edge for Private Cloud because this module is statically compiled into NGINX.

Impact on Apigee Edge for Private Cloud:

Apigee Edge for Private Cloud is not affected by this vulnerability in its default, shipped configuration. The exploitability of CVE-2026-42945 is dependent on specific NGINX configuration patterns, notably the use of the rewrite directive in a particular sequence. These patterns are not present in any standard Apigee Edge for Private Cloud NGINX configurations.

Action Required:

• For Default Apigee Edge for Private Cloud Configurations: No patches, upgrades, or operational changes are required. Scanner findings regarding CVE-2026-42945 can be treated as false positives for default installations. You can use the following text to document this exception in your vulnerability management system:

  CVE-2026-42945 — Accepted exception (false positive for Apigee Edge for Private Cloud). Apigee Edge for Private Cloud does not use the rewrite directive in any shipped NGINX configuration. The vulnerable code path in ngx_http_rewrite_module is configuration-gated and is not reachable in the default Apigee Edge for Private Cloud deployment.

• For Customized NGINX Configurations: If you have manually modified the NGINX configuration files within your Apigee Edge for Private Cloud installation (for example, under /opt/nginx), you should perform the following self-check to ensure your customizations have not inadvertently introduced the vulnerable pattern:
  1. Check for rewrite directive: On each NGINX node, run the command:

     sudo grep -rnI '^\s*rewrite\b' /opt/nginx

  2. Analyze Results:
     • If the command returns no output, your system is not affected.
     • If matches are found, review each instance. The vulnerability is present only if all the following conditions are met for a given block:
       • The rewrite directive is used.
       • It is immediately followed by another rewrite, if, or set directive within the same configuration block.
       • An unnamed PCRE capture group (for example, $1, $2, etc.) is used in the directives.
       • The replacement string in the directive contains a question mark (?).
  3. Mitigation (if vulnerable): If all the above conditions are true for any part of your custom configuration, mitigate by:
     • Removing the question mark (?) from the replacement string.
     • Using named PCRE capture groups instead of unnamed ones.
     • Re-evaluating the need for the chained directives.

In Edge for Private Cloud 4.53.00 and later, the UI displays an "End of Life" (EOL) warning pop-up. This warning appears
repeatedly and cannot be prevented or reduced in frequency.

There is currently no method available for users to disable or reduce the frequency of this EOL warning.

Customer Java callouts that attempt to load the Bouncy Castle cryptography provider using the name "BC" might fail because the default provider has been changed to Bouncy Castle FIPS to support FIPS. The new provider name to use is "BCFIPS".

Customer Java callouts that attempt to load the Bouncy Castle cryptography provider using the name "BC" might fail because the default provider has been changed to Bouncy Castle FIPS to support FIPS. The new provider name to use is "BCFIPS".

This issue affects only those who are using MINT or have MINT enabled in Edge for Private Cloud installations.

Component affected: edge-message-processor

Issue: If you have monetization enabled and are installing 4.52.01 as a fresh install or upgrading from previous Private Cloud versions, you will encounter an issue with message processors. There will be a gradual increase in open thread count leading to resource exhaustion. The following exception is seen in edge-message-processor system.log:

Error injecting constructor, java.lang.OutOfMemoryError: unable to create new native thread

A Denial-of-Service (DoS) vulnerability was recently discovered in multiple implementations of the HTTP/2 protocol (CVE-2023-44487), including in Apigee Edge for Private Cloud. The vulnerability could lead to a DoS of Apigee API management functionality. For more details, see Apigee Security Bulletin GCP-2023-032.

The Edge for Private Cloud router and management server components are exposed to the internet and can potentially be vulnerable. Although HTTP/2 is enabled on the management port of other Edge-specific components of Edge for Private Cloud, none of those components are exposed to the internet. On non-Edge components, like Cassandra, Zookeeper and others, HTTP/2 is not enabled. We recommend that you take the following steps to address the Edge for Private Cloud vulnerability:

• Steps for Edge for Private Cloud versions 4.51.00.11 or newer
• Steps for Edge for Private Cloud versions older than 4.51.00.11

Follow these steps if you are using Edge Private Cloud versions 4.51.00.11 or newer:

1. Update the management server:

   1. On each management server node, open /opt/apigee/customer/application/management-server.properties
   2. Add this line to the properties file:

      conf_webserver_http2.enabled=false

   3. Restart the management server component:

      apigee-service edge-management-server restart

2. Update the message processor:

   1. On each message processor node, open /opt/apigee/customer/application/message-processor.properties
   2. Add this line to the properties file:

      conf_webserver_http2.enabled=false

   3. Restart the message processor component:

      apigee-service edge-message-processor restart

3. Update the router:

   1. On each router node, open /opt/apigee/customer/application/router.properties
   2. Add this line to the properties file:

      conf_webserver_http2.enabled=false

   3. Restart the message processor component:

      apigee-service edge-router restart

4. Update QPID:

   1. On each QPID node, open /opt/apigee/customer/application/qpid-server.properties
   2. Add this line to the properties file:

      conf_webserver_http2.enabled=false

   3. Restart the message processor component:

      apigee-service edge-qpid-server restart

5. Update Postgres:

   1. On each Postgres node, open /opt/apigee/customer/application/postgres-server.properties
   2. Add this line to the properties file:

      conf_webserver_http2.enabled=false

   3. Restart the message processor component:

      apigee-service edge-postgres-server restart

Follow these steps if you are using Edge for Private Cloud versions older than 4.51.00.11:

1. Update the management server:

   1. On each management server node, open /opt/apigee/customer/application/management-server.properties
   2. Add the following two lines to the properties file:

      conf_webserver_http2.enabled=false
      conf/webserver.properties+http2.enabled=false

   3. Restart the management server component:

      apigee-service edge-management-server restart

2. Update the message processor:

   1. On each message processor node, open /opt/apigee/customer/application/message-processor.properties
   2. Add the following two lines to the properties file:

      conf_webserver_http2.enabled=false
      conf/webserver.properties+http2.enabled=false

   3. Restart the message processor component:

      apigee-service edge-message-processor restart

3. Update the router:

   1. On each router node, open /opt/apigee/customer/application/router.properties
   2. Add the following two lines to the properties file:

      conf_webserver_http2.enabled=false
      conf/webserver.properties+http2.enabled=false

   3. Restart the message processor component:

      apigee-service edge-router restart

4. Update QPID:

   1. On each QPID node, open /opt/apigee/customer/application/qpid-server.properties
   2. Add the following two lines to the properties file:

      conf_webserver_http2.enabled=false
      conf/webserver.properties+http2.enabled=false

   3. Restart the message processor component:

      apigee-service edge-qpid-server restart

5. Update Postgres:

   1. On each Postgres node, open /opt/apigee/customer/application/postgres-server.properties
   2. Add the following two lines to the properties file:

      conf_webserver_http2.enabled=false
      conf/webserver.properties+http2.enabled=false

   3. Restart the message processor component:

      apigee-service edge-postgres-server restart

Apigee-postgresql is having issues with upgrading from Edge for Private Cloud version 4.50 or 4.51 to version 4.52. The issues mainly occur when the number of tables is greater than 500.

You can check the total number of tables in Postgres by running the SQL query below:

select count(*) from information_schema.tables

Workaround: When Updating Apigee Edge 4.50.00 or 4.51.00 to 4.52.00, be sure to perform the preliminary step before upgrading Apigee-postgresql.

149245401: LDAP connection pool settings for JNDI configured through the LDAP resource are not reflected, and JNDI defaults cause single-use connections each time. As a result, connections are being opened and closed each time for single use, creating a large number of connections per hour to the LDAP server.

Workaround:

In order to change the LDAP connection pool properties, do the following steps to set a global change across all LDAP policies.

1. Create a configuration properties file if it does not already exist:

   /opt/apigee/customer/application/message-processor.properties

2. Add the following to the file (replace values of Java Naming and Directory Interface (JNDI) properties based on your LDAP resource configuration requirement).

   bin_setenv_ext_jvm_opts="-Dcom.sun.jndi.ldap.connect.pool.maxsize=20
   -Dcom.sun.jndi.ldap.connect.pool.prefsize=2
   -Dcom.sun.jndi.ldap.connect.pool.initsize=2
   -Dcom.sun.jndi.ldap.connect.pool.timeout=120000
   -Dcom.sun.jndi.ldap.connect.pool.protocol=ssl"

3. Make sure the file /opt/apigee/customer/application/message-processor.properties is owned by apigee:apigee.
4. Restart each message processor.

To verify that your connection pool JNDI properties are taking effect, you can perform a tcpdump to observe the behavior of the LDAP connection pool over time.

139051927: High proxy processing latencies found in the Message Processor are affecting all API Proxies. Symptoms include 200-300ms delays in processing times over normal API response times and can occur randomly even with low TPS. This can occur when than more than 50 target servers in which a message processor makes connections.

Root cause: Message processors keep a cache that maps target server URL to HTTPClient object for outgoing connections to target servers. By default this setting is set to 50 which may be too low for most deployments. When a deployment has multiple org/env combinations in a setup, and have a large number of target servers that exceed 50 altogether, the target server URLs keep getting evicted from cache, causing latencies.

Validation: To determine if target server URL eviction is causing the latency problem, search the Message Processor system.logs for keyword "onEvict" or "Eviction". Their presence in the logs indicate that target server URLs are getting evicted from the HTTPClient cache because the cache size is too small.

Workaround: For Edge for Private Cloud versions 19.01 and 19.06, you can edit and configure the HTTPClient cache, /opt/apigee/customer/application/message-processor.properties:

conf/http.properties+HTTPClient.dynamic.cache.elements.size=500

Then restart the message processor. Make the same changes for all message processors.

The value 500 is an example. The optimal value for your setup should be greater than the number of target servers that the message processor would connect to. There are no side effects from setting this property higher, and the only affect would be an improved message processor proxy request processing times.

Note: Edge for Private Cloud version 50.00 has the default setting of 500.

157933959: Concurrent inserts and updates to the same key value map (KVM) scoped to the organization or environment level causes inconsistent data and lost updates.

Note: This limitation only applies to Edge for Private Cloud. Edge for Public Cloud and Hybrid do not have this limitation.

For a workaround in Edge for Private Cloud, create the KVM at the apiproxy scope.