You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/spring-cloud/how-to-use-enterprise-api-portal.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -79,7 +79,7 @@ az spring api-portal update --assign-endpoint
79
79
80
80
This section describes how to view and try out APIs with schema definitions in API portal. Use the following steps to configure API routing with an OpenAPI spec URL on Spring Cloud Gateway for Tanzu.
81
81
82
-
1. Create an app in Azure Spring Apps which the gateway will route traffic to.
82
+
1. Create an app in Azure Spring Apps that the gateway will route traffic to.
83
83
84
84
1. Generate the OpenAPI definition and get the URI to access it. The following two URI options are accepted:
Copy file name to clipboardExpand all lines: articles/spring-cloud/how-to-use-enterprise-spring-cloud-gateway.md
+11-5Lines changed: 11 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,13 @@ This article shows you how to use Spring Cloud Gateway for VMware Tanzu® with A
21
21
22
22
[Spring Cloud Gateway for Tanzu](https://docs.vmware.com/en/VMware-Spring-Cloud-Gateway-for-Kubernetes/index.html) is one of the commercial VMware Tanzu components. It's based on the open-source Spring Cloud Gateway project. Spring Cloud Gateway for Tanzu handles cross-cutting concerns for API development teams, such as single sign-on (SSO), access control, rate-limiting, resiliency, security, and more. You can accelerate API delivery using modern cloud native patterns, and any programming language you choose for API development.
23
23
24
-
Spring Cloud Gateway for Tanzu also has other commercial API route filters for transporting authorized JSON Web Token (JWT) claims to application services, client certificate authorization, rate-limiting approaches, circuit breaker configuration, and support for accessing application services via HTTP Basic Authentication credentials.
24
+
Spring Cloud Gateway for Tanzu also has the following features:
25
+
26
+
- Other commercial API route filters for transporting authorized JSON Web Token (JWT) claims to application services.
27
+
- Client certificate authorization.
28
+
- Rate-limiting approaches.
29
+
- Circuit breaker configuration.
30
+
- Support for accessing application services via HTTP Basic Authentication credentials.
25
31
26
32
To integrate with [API portal for VMware Tanzu®](./how-to-use-enterprise-api-portal.md), Spring Cloud Gateway for Tanzu automatically generates OpenAPI version 3 documentation after the route configuration gets changed.
27
33
@@ -84,7 +90,7 @@ Cross-origin resource sharing (CORS) allows restricted resources on a web page t
84
90
85
91
### Configure single sign-on (SSO)
86
92
87
-
Spring Cloud Gateway for Tanzu supports authentication and authorization using single sign-on (SSO) with an OpenID identity provider (IdP) which supports OpenID Connect Discovery protocol.
93
+
Spring Cloud Gateway for Tanzu supports authentication and authorization using single sign-on (SSO) with an OpenID identity provider (IdP) that supports OpenID Connect Discovery protocol.
@@ -117,10 +123,10 @@ This section describes how to add, update, and manage API routes for apps that u
117
123
118
124
The route config definition includes the following parts:
119
125
120
-
- OpenAPI URI: The URI points to an OpenAPI specification. Both OpenAPI 2.0 and OpenAPI 3.0 specs are supported. The specification can be shown in API portal to try out. Two types of URI are accepted. The first type of URI is a public endpoint like `https://petstore3.swagger.io/api/v3/openapi.json`. The second type of URI is a constructed URL `http://<app-name>/{relative-path-to-OpenAPI-spec}`, where `app-name` is the name of an application in Azure Spring Apps which includes the API definition.
126
+
- OpenAPI URI: The URI points to an OpenAPI specification. Both OpenAPI 2.0 and OpenAPI 3.0 specs are supported. The specification can be shown in API portal to try out. Two types of URI are accepted. The first type of URI is a public endpoint like `https://petstore3.swagger.io/api/v3/openapi.json`. The second type of URI is a constructed URL `http://<app-name>/{relative-path-to-OpenAPI-spec}`, where `app-name` is the name of an application in Azure Spring Apps that includes the API definition.
121
127
- routes: A list of route rules about how the traffic goes to one app.
122
128
123
-
Use the following command to create a route config. The `--app-name` value should be the name of an app hosted in Azure Spring Apps which the requests will route to.
129
+
Use the following command to create a route config. The `--app-name` value should be the name of an app hosted in Azure Spring Apps that the requests will route to.
124
130
125
131
```azurecli
126
132
az spring gateway route-config create \
@@ -179,7 +185,7 @@ Not all the filters/predicates are supported in Azure Spring Apps because of sec
179
185
180
186
Use the following steps to create an example application using Spring Cloud Gateway for Tanzu.
181
187
182
-
1. To create an app in Azure Spring Apps which the Spring Cloud Gateway for Tanzu would route traffic to, follow the instructions in [Quickstart: Build and deploy apps to Azure Spring Apps using the Enterprise tier](quickstart-deploy-apps-enterprise.md). Select `customers-service` for this example.
188
+
1. To create an app in Azure Spring Apps that the Spring Cloud Gateway for Tanzu would route traffic to, follow the instructions in [Quickstart: Build and deploy apps to Azure Spring Apps using the Enterprise tier](quickstart-deploy-apps-enterprise.md). Select `customers-service` for this example.
183
189
184
190
1. Assign a public endpoint to the gateway to access it.
0 commit comments