Skip to content

Commit 59debb4

Browse files
Edits
1 parent 8a916c0 commit 59debb4

1 file changed

Lines changed: 21 additions & 17 deletions

File tree

modules/ROOT/pages/_partials/task-configure-proxy.adoc

Lines changed: 21 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -124,27 +124,31 @@ NOTE: Anypoint API Manager supports OpenAPI Specification (OAS) 3.0, with the ex
124124
[[configure_options]]
125125
= Configure Options
126126

127-
. Enter your *Implementation URI*. The Implementation URI is the URL to access the proxy or the API. For example, you can use the URL of your API asset in Exchange. +
128-
This is the only required field. For further details on the optional fields, see xref:configure-api-task.adoc[Configure an API Endpoint].
129-
. If you want to enable SSL for inbound traffic:
130-
** Select **HTTPS** for the **Scheme**. +
131-
You should now see the **TLS Context for Inbound Traffic** field enabled.
132-
** Select **Add TLS Context**.
133-
*** Select the secret group where you hosted your TLS context from the **Secret group** drop-down.
134-
*** Select your TLS context for your HTTPS API Proxy from the **TLS Context** drop-down.
135-
. Enter the *Port* number for your API proxy.
136-
. Select your *Client Provider*.
137-
. Click *Advanced Options*.
138-
. In *Proxy Version*, select *latest*. +
139-
This value ensures that your API proxy uses the latest released proxy version.
140-
If a new proxy version is available in Anypoint platform, return to this step to reconfigure your proxy to the latest version.
141-
. Click *Add TLS Context* for *TLS Context for Outbound traffic*.
127+
. Configure the downstream:
128+
+
129+
include::partial$api-configuration-tables.adoc[tags=mule-proxy-downstream]
130+
+
131+
[NOTE]
132+
====
133+
To add a TLS context:
134+
. Click *Add TLS Context* for the relevant TLS direction.
142135
.. Select the secret group where you hosted your TLS Context from the *Secret Group* drop-down list.
143136
.. Select your TLS Context for your HTTPS API Proxy from the *TLS Context* drop-down.
137+
====
138+
+
139+
. Click *Next*.
140+
. Configure the upstream:
141+
+
142+
include::partial$api-configuration-tables.adoc[tags=mule-proxy-upstream]
144143
+
145144
[NOTE]
146-
If you can't see a context, check that you have the right permissions, as mentioned in <<Before You Begin>>.
147-
145+
====
146+
To add a TLS context:
147+
. Click *Add TLS Context* for the relevant TLS direction.
148+
.. Select the secret group where you hosted your TLS Context from the *Secret Group* drop-down list.
149+
.. Select your TLS Context for your HTTPS API Proxy from the *TLS Context* drop-down.
150+
====
151+
+
148152
. Click *Next*.
149153
//end::mid-steps2[]
150154
//tag::raml-oas-version[]

0 commit comments

Comments
 (0)