search

forcedotcom / try-acb-feedback

BSD 3-Clause "New" or "Revised" License
3 stars 1 forks source link

Used *.mulesoft.com domains are not trusted per default #22

Closed muenzpraeger closed 1 year ago

muenzpraeger commented 1 year ago

Is your feature request related to a problem? Please describe. MuleSoft domains that are used throughout ACB are not trusted by default (i. e. anypoint.mulesoft.com, docs.mulesoft.com etc). image

Describe what you are ultimately trying to do As this is a vendor-controlled environment the expectation is that vender-sites are trusted-by-default, so that users don't have to go through unnecessary hoops.

vchirag-mulesoft commented 1 year ago

Hi @muenzpraeger,

Thank you for logging the issue with MuleSoft.

We need to connect to Mulesoft domains to design API, retrieve an asset from the exchange, and deploy the app to ARM. We connect to Mulesoft domains as we currently have in Studio. We can create a doc to allow/whitelist the list of domains.

Please let us know your thoughts.

muenzpraeger commented 1 year ago

The used domains (i. e. wildcarded *.mulesoft.com) should come pre-trusted on an ACB instance.

simoneegeib commented 1 year ago

Thank you for sharing your feature request. An enhancement has been filed and will be reviewed by our team.. We will get back to you if we need additional information.