From 7da18510f568fc9670940331ae5b18089c370ba8 Mon Sep 17 00:00:00 2001 From: Glenn Rodgers Date: Wed, 13 Nov 2024 11:00:30 -0500 Subject: [PATCH 1/6] Update flex-review-prerequisites.adoc --- .../ROOT/pages/flex-review-prerequisites.adoc | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/gateway/1.9/modules/ROOT/pages/flex-review-prerequisites.adoc b/gateway/1.9/modules/ROOT/pages/flex-review-prerequisites.adoc index 04ba3830f..528ff4834 100644 --- a/gateway/1.9/modules/ROOT/pages/flex-review-prerequisites.adoc +++ b/gateway/1.9/modules/ROOT/pages/flex-review-prerequisites.adoc @@ -158,3 +158,21 @@ For Flex Gateway to communicate with MuleSoft-managed online Anypoint Platform A ==== Port 9998 is reserved for internal processes, and should not be used in `ApiInstance` definitions. ==== + +[[flex-gateway-hyperforce]] +== Flex Gateway on Hyperforce + +Hyperforce supports Flex Gateway versions 1.7 and later. Because Flex Gateway running in Local Mode is completely self-hosted, it is not affected by Hyperforce. For Flex Gateway running in Connected Mode, API Manager control plane does not support the following features: + +* API Alerts ++ +See xref:flex-use-api-alerts.adoc[]. + +* Key Metrics ++ +See xref:flex-view-api-metrics.adoc[]. + +For more information about API Managers support on Hyperforce, see xref:api-manager + + + \ No newline at end of file From cca09f32442f63efefc0399e29ea359929a00104 Mon Sep 17 00:00:00 2001 From: Glenn Rodgers Date: Wed, 13 Nov 2024 11:51:46 -0500 Subject: [PATCH 2/6] Update mule-gateway-capabilities-mule4.adoc --- .../mule-gateway-capabilities-mule4.adoc | 50 +++++++++++++++++++ 1 file changed, 50 insertions(+) diff --git a/mule-gateway/modules/ROOT/pages/mule-gateway-capabilities-mule4.adoc b/mule-gateway/modules/ROOT/pages/mule-gateway-capabilities-mule4.adoc index 82ca2723f..2a067994b 100644 --- a/mule-gateway/modules/ROOT/pages/mule-gateway-capabilities-mule4.adoc +++ b/mule-gateway/modules/ROOT/pages/mule-gateway-capabilities-mule4.adoc @@ -137,6 +137,56 @@ Depending on your implementation, there are several ways to pass organization cr See xref:api-manager::org-credentials-config-mule4.adoc[Configuring Organization Credentials in Mule Runtime 4] or xref:api-manager::org-credentials-config-mule3.adoc[Mule Runtime 3] to learn how to do this. +[[mule-gateway-hyperforce]] +== Mule Gateway on Hyperforce + +All features of Mule Gateway are supported on Hyperforce with these exceptions: + +* API Alerts +* Key Metrics + +=== Mule Gateway Proxies on Hyperforce + +All Mule Gateway proxies are supported on Hyperforce. See the following table to find the first proxy versions that are supported on Hyperforce: + +[%header%autowidth.spread] +|=== +|Policy |Version +| HTTP Proxy |2.1.1 +| HTTPS Proxy |2.1.1 +| REST Proxy |3.2.2 and 2.2.1 +| WSDL Proxy |3.1.3 and 2.2.1 +|=== + +=== Mule Gateway Policies on Hyperforce + +All Mule Gateway policies are supported on Hyperforce. See the following table to find the first policy definition and implementation versions that are supported on Hyperforce: + +[%header%autowidth.spread] +|=== +|Policy |Definition |Implementation +| Basic Authentication: LDAP |1.4.0 |1.4.1 +| Basic Authentication: Simple |1.3.1 |1.4.1 +| Client ID Enforcement |1.3.2 |1.4.0 +| Cross-Origin Resource Sharing (CORS) |1.3.1 |1.4.1 +| Header Injection |1.3.1 |1.4.0 +| Header Removal |1.1.1 |1.2.0 +| HTTP Caching |1.1.0 |1.1.0 +| IP Allowlist |1.1.1 |1.2.0 +| IP Blocklist |1.1.1 |1.2.0 +| JSON Threat Protection |1.2.0 |1.2.3 +| JWT Validation |1.4.0 |1.4.1 +| Message Logging |2.0.1 |2.1.1 +| OAuth 2.0 Access Token Enforcement Using Mule OAuth Provider |1.6.0 |1.6.1 +| OpenAM OAuth 2.0 Token Enforcement |1.6.0 |1.6.1 +| OpenID Connect OAuth 2.0 Access Token Enforcement |1.6.0 |1.6.1 +| PingFederate OAuth 2.0 Token Enforcement |1.6.0 |1.6.1 +| Rate Limiting |1.4.0 |1.4.0 +| Rate Limiting: SLA-based |1.3.0 |1.3.0 +| Spike Control |1.2.1 |1.3.1 +| XML Threat Protection |1.2.0 |1.2.0 +|=== + == See Also * xref:api-manager::api-auto-discovery-new-concept.adoc[Reviewing Mule Gateway API Autodiscovery concepts] From 4630ed9e541bb49f389b615e9286261065f4e0a7 Mon Sep 17 00:00:00 2001 From: Glenn Rodgers Date: Wed, 13 Nov 2024 13:09:21 -0500 Subject: [PATCH 3/6] Edits --- gateway/1.9/modules/ROOT/pages/flex-review-prerequisites.adoc | 2 +- gateway/1.9/modules/ROOT/pages/flex-use-api-alerts.adoc | 3 +++ gateway/1.9/modules/ROOT/pages/flex-view-api-metrics.adoc | 2 ++ .../modules/ROOT/pages/mule-gateway-capabilities-mule4.adoc | 2 ++ 4 files changed, 8 insertions(+), 1 deletion(-) diff --git a/gateway/1.9/modules/ROOT/pages/flex-review-prerequisites.adoc b/gateway/1.9/modules/ROOT/pages/flex-review-prerequisites.adoc index 528ff4834..4aac2f40b 100644 --- a/gateway/1.9/modules/ROOT/pages/flex-review-prerequisites.adoc +++ b/gateway/1.9/modules/ROOT/pages/flex-review-prerequisites.adoc @@ -172,7 +172,7 @@ See xref:flex-use-api-alerts.adoc[]. + See xref:flex-view-api-metrics.adoc[]. -For more information about API Managers support on Hyperforce, see xref:api-manager +For more information about API Manager's support on Hyperforce, see xref:api-manager \ No newline at end of file diff --git a/gateway/1.9/modules/ROOT/pages/flex-use-api-alerts.adoc b/gateway/1.9/modules/ROOT/pages/flex-use-api-alerts.adoc index c18158d40..6458c1637 100644 --- a/gateway/1.9/modules/ROOT/pages/flex-use-api-alerts.adoc +++ b/gateway/1.9/modules/ROOT/pages/flex-use-api-alerts.adoc @@ -4,6 +4,9 @@ include::_attributes.adoc[] endif::[] :imagesdir: ../assets/images +[NOTE] +Hyperforce deployments do not support API Alerts. + Using API alerts for Flex Gateway in Connected Mode, you can add and configure email notifications that flag unusual API behavior, such as: * An API response time over 60 seconds diff --git a/gateway/1.9/modules/ROOT/pages/flex-view-api-metrics.adoc b/gateway/1.9/modules/ROOT/pages/flex-view-api-metrics.adoc index d89b70e49..169aa5fcf 100644 --- a/gateway/1.9/modules/ROOT/pages/flex-view-api-metrics.adoc +++ b/gateway/1.9/modules/ROOT/pages/flex-view-api-metrics.adoc @@ -4,6 +4,8 @@ include::_attributes.adoc[] endif::[] :imagesdir: ../assets/images +[NOTE] +Hyperforce deployments do not support Key Metrics. API Manager and Anypoint Monitoring collect metrics on active Flex Gateway API instances. You can view charts related to these metrics and filter the data by date. diff --git a/mule-gateway/modules/ROOT/pages/mule-gateway-capabilities-mule4.adoc b/mule-gateway/modules/ROOT/pages/mule-gateway-capabilities-mule4.adoc index 2a067994b..f246354f3 100644 --- a/mule-gateway/modules/ROOT/pages/mule-gateway-capabilities-mule4.adoc +++ b/mule-gateway/modules/ROOT/pages/mule-gateway-capabilities-mule4.adoc @@ -145,6 +145,8 @@ All features of Mule Gateway are supported on Hyperforce with these exceptions: * API Alerts * Key Metrics +For more information about API Manager's support on Hyperforce, see xref:api-manager + === Mule Gateway Proxies on Hyperforce All Mule Gateway proxies are supported on Hyperforce. See the following table to find the first proxy versions that are supported on Hyperforce: From eba1bbe9154486258e1fe5b4799941a0a546c933 Mon Sep 17 00:00:00 2001 From: Glenn Rodgers Date: Wed, 13 Nov 2024 13:12:33 -0500 Subject: [PATCH 4/6] Update flex-review-prerequisites.adoc --- .../1.9/modules/ROOT/pages/flex-review-prerequisites.adoc | 7 ------- 1 file changed, 7 deletions(-) diff --git a/gateway/1.9/modules/ROOT/pages/flex-review-prerequisites.adoc b/gateway/1.9/modules/ROOT/pages/flex-review-prerequisites.adoc index 4aac2f40b..54e88287e 100644 --- a/gateway/1.9/modules/ROOT/pages/flex-review-prerequisites.adoc +++ b/gateway/1.9/modules/ROOT/pages/flex-review-prerequisites.adoc @@ -165,14 +165,7 @@ Port 9998 is reserved for internal processes, and should not be used in `ApiInst Hyperforce supports Flex Gateway versions 1.7 and later. Because Flex Gateway running in Local Mode is completely self-hosted, it is not affected by Hyperforce. For Flex Gateway running in Connected Mode, API Manager control plane does not support the following features: * API Alerts -+ -See xref:flex-use-api-alerts.adoc[]. - * Key Metrics -+ -See xref:flex-view-api-metrics.adoc[]. - -For more information about API Manager's support on Hyperforce, see xref:api-manager \ No newline at end of file From c3ed53b0ef0fbbb5018f032e6570acf2d3a2b6c0 Mon Sep 17 00:00:00 2001 From: Glenn Rodgers Date: Wed, 27 Nov 2024 09:30:24 -0600 Subject: [PATCH 5/6] Remove mule gateway --- .../ROOT/pages/flex-use-api-alerts.adoc | 2 +- .../ROOT/pages/flex-view-api-metrics.adoc | 2 +- .../mule-gateway-capabilities-mule4.adoc | 52 ------------------- 3 files changed, 2 insertions(+), 54 deletions(-) diff --git a/gateway/1.9/modules/ROOT/pages/flex-use-api-alerts.adoc b/gateway/1.9/modules/ROOT/pages/flex-use-api-alerts.adoc index 6458c1637..49dc575c7 100644 --- a/gateway/1.9/modules/ROOT/pages/flex-use-api-alerts.adoc +++ b/gateway/1.9/modules/ROOT/pages/flex-use-api-alerts.adoc @@ -5,7 +5,7 @@ endif::[] :imagesdir: ../assets/images [NOTE] -Hyperforce deployments do not support API Alerts. +Hyperforce deployments don't support API Alerts. Using API alerts for Flex Gateway in Connected Mode, you can add and configure email notifications that flag unusual API behavior, such as: diff --git a/gateway/1.9/modules/ROOT/pages/flex-view-api-metrics.adoc b/gateway/1.9/modules/ROOT/pages/flex-view-api-metrics.adoc index 169aa5fcf..f2a741919 100644 --- a/gateway/1.9/modules/ROOT/pages/flex-view-api-metrics.adoc +++ b/gateway/1.9/modules/ROOT/pages/flex-view-api-metrics.adoc @@ -5,7 +5,7 @@ endif::[] :imagesdir: ../assets/images [NOTE] -Hyperforce deployments do not support Key Metrics. +Hyperforce deployments don't support Key Metrics. API Manager and Anypoint Monitoring collect metrics on active Flex Gateway API instances. You can view charts related to these metrics and filter the data by date. diff --git a/mule-gateway/modules/ROOT/pages/mule-gateway-capabilities-mule4.adoc b/mule-gateway/modules/ROOT/pages/mule-gateway-capabilities-mule4.adoc index f246354f3..82ca2723f 100644 --- a/mule-gateway/modules/ROOT/pages/mule-gateway-capabilities-mule4.adoc +++ b/mule-gateway/modules/ROOT/pages/mule-gateway-capabilities-mule4.adoc @@ -137,58 +137,6 @@ Depending on your implementation, there are several ways to pass organization cr See xref:api-manager::org-credentials-config-mule4.adoc[Configuring Organization Credentials in Mule Runtime 4] or xref:api-manager::org-credentials-config-mule3.adoc[Mule Runtime 3] to learn how to do this. -[[mule-gateway-hyperforce]] -== Mule Gateway on Hyperforce - -All features of Mule Gateway are supported on Hyperforce with these exceptions: - -* API Alerts -* Key Metrics - -For more information about API Manager's support on Hyperforce, see xref:api-manager - -=== Mule Gateway Proxies on Hyperforce - -All Mule Gateway proxies are supported on Hyperforce. See the following table to find the first proxy versions that are supported on Hyperforce: - -[%header%autowidth.spread] -|=== -|Policy |Version -| HTTP Proxy |2.1.1 -| HTTPS Proxy |2.1.1 -| REST Proxy |3.2.2 and 2.2.1 -| WSDL Proxy |3.1.3 and 2.2.1 -|=== - -=== Mule Gateway Policies on Hyperforce - -All Mule Gateway policies are supported on Hyperforce. See the following table to find the first policy definition and implementation versions that are supported on Hyperforce: - -[%header%autowidth.spread] -|=== -|Policy |Definition |Implementation -| Basic Authentication: LDAP |1.4.0 |1.4.1 -| Basic Authentication: Simple |1.3.1 |1.4.1 -| Client ID Enforcement |1.3.2 |1.4.0 -| Cross-Origin Resource Sharing (CORS) |1.3.1 |1.4.1 -| Header Injection |1.3.1 |1.4.0 -| Header Removal |1.1.1 |1.2.0 -| HTTP Caching |1.1.0 |1.1.0 -| IP Allowlist |1.1.1 |1.2.0 -| IP Blocklist |1.1.1 |1.2.0 -| JSON Threat Protection |1.2.0 |1.2.3 -| JWT Validation |1.4.0 |1.4.1 -| Message Logging |2.0.1 |2.1.1 -| OAuth 2.0 Access Token Enforcement Using Mule OAuth Provider |1.6.0 |1.6.1 -| OpenAM OAuth 2.0 Token Enforcement |1.6.0 |1.6.1 -| OpenID Connect OAuth 2.0 Access Token Enforcement |1.6.0 |1.6.1 -| PingFederate OAuth 2.0 Token Enforcement |1.6.0 |1.6.1 -| Rate Limiting |1.4.0 |1.4.0 -| Rate Limiting: SLA-based |1.3.0 |1.3.0 -| Spike Control |1.2.1 |1.3.1 -| XML Threat Protection |1.2.0 |1.2.0 -|=== - == See Also * xref:api-manager::api-auto-discovery-new-concept.adoc[Reviewing Mule Gateway API Autodiscovery concepts] From 3c73209077b3e83680baaae06380cd4209fa59ed Mon Sep 17 00:00:00 2001 From: Glenn Rodgers Date: Wed, 27 Nov 2024 09:35:47 -0600 Subject: [PATCH 6/6] Update flex-review-prerequisites.adoc --- gateway/1.9/modules/ROOT/pages/flex-review-prerequisites.adoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/gateway/1.9/modules/ROOT/pages/flex-review-prerequisites.adoc b/gateway/1.9/modules/ROOT/pages/flex-review-prerequisites.adoc index 44193237c..7771ce970 100644 --- a/gateway/1.9/modules/ROOT/pages/flex-review-prerequisites.adoc +++ b/gateway/1.9/modules/ROOT/pages/flex-review-prerequisites.adoc @@ -158,5 +158,7 @@ Hyperforce supports Flex Gateway versions 1.7 and later. Because Flex Gateway ru * API Alerts * Key Metrics +For more information about API Manager's support on Hyperforce, see xref:api-manager::latest-overview-concept.adoc#APIM-hyperforce[API Manager on Hyperforce]. + \ No newline at end of file