Feature: Retrieve Safe Apps only guaranteed to work on the current client

[mmv08]

What it solves

Resolves #2672 where apps limited access to embedding it as an iframe to specific origins

How this PR fixes it

So now, for GET /safe-apps, there's a clientUrl param available on the client gateway and config service. It takes a hostname with a protocol, and the returned apps are ensured to work on this client.

How to test it

1. Load the mainnet Safe deployment
2. Zerion or 1inch shouldn't be on the list of safe apps

[github-actions]

CLA Assistant Lite All Contributors have signed the CLA.

[github-actions]

ESLint Summary View Full Report

Annotations are provided inline on the Files Changed tab. You can also see all annotations that were generated on the annotations page.

Type	Occurrences	Fixable
Errors	0	0
Warnings	0	0
Ignored	2	N/A

• Result: ✅ success
• Annotations: 0 total

---

^{Report generated by eslint-plus-action}

[github-actions]

Deployment links

🟠 Safe Rinkeby	⚪ Safe Mainnet	🟣 Safe Polygon	🟡 Safe BSC	⚫ Safe Arbitrum	🟢 Safe xDai

[github-actions]

E2E Tests Failed
Check the results here: https://github.com/gnosis/safe-react-e2e-tests/actions/runs/1697661767

Failed tests:

• ❌ Safe Apps List Safe Apps List
• ❌ Safe Balances Safe Balances

[coveralls]

Pull Request Test Coverage Report for Build 1697629199

• 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 32.44%

---

Totals
Change from base Build 1696744828:	0.0%
Covered Lines:	3123
Relevant Lines:	8571

---

💛 - Coveralls

[iamacook]

Looks good to me

[katspaugh]

👍

[mmv08]

Screen.Recording.2022-01-14.at.15.22.40.mov

The issue reported by @JagoFigueroa in the original issue was because the build used prod backend where correct accessControls are not set yet. When using staging endpoints it works perfectly (check video)

[JagoFigueroa]

Thank you @mikheevm ! I think it's more than fair to close this ticket then ;)