-
Story
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
Yes
-
DevX 18, DevX 21
-
3
On SaaS, all the access from Magnolia instances to external URLs, will be done using a proxy, to enforce security.
That's the reason why two things must be accomplished here:
MGNLRESTCL-14- Retrieve the proxy to be used from configuration, as it is currently being done from microprofile file for other services.
To sum up, this story must ensure that REST client uses the SaaS deployed proxy. For that, it must:
- Check if the Rest Client is running on a SaaS instance.
- Read the configuration using microprofile (as for example, it's being done with info.magnolia.config.subscriptionService.endpoint), if we are on SaaS.
- Automatically add that proxy to each RestClientDefinition configured.
The estimation here only refers to the configuration part, not the support for proxies on REST client (that will be managed in MGNLRESTCL-14)
Also, upgrade REST client dependency on Webhooks module to 3.0 version.
- depends upon
-
MGNLRESTCL-14 Using the restclient with a proxy server
- Closed
- duplicates
-
MGNLHOOK-190 Merge Webhooks integration on SaaS when changes on Rest Client are done
- Closed
- is depended upon by
-
MGNLHOOK-190 Merge Webhooks integration on SaaS when changes on Rest Client are done
- Closed
- split from
-
MGNLHOOK-25 Take back REST client to SaaS
- Closed
- supersedes
-
MGNLHOOK-189 Upgrade Rest Client version to 3.0
- Closed
1.
|
Implement proxy usage on SaaS for Rest Client | Completed | Javier Benito | |||||||||
2.
|
Review | Completed | Robert Šiška | |||||||||
3.
|
piQA | Completed | Dai Ha | |||||||||
4.
|
QA | Completed | Oanh Thai Hoang |
|
||||||||
5.
|
Testing on SaaS staging with Norsu | Completed | Javier Benito | |||||||||
6.
|
2nd round review | Completed | Canh Nguyen |