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
. Click *Add TLS Context* for the relevant TLS direction.
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*.
135
142
.. Select the secret group where you hosted your TLS Context from the *Secret Group* drop-down list.
136
143
.. Select your TLS Context for your HTTPS API Proxy from the *TLS Context* drop-down.
0 commit comments