diff options
| author | Robot Odoo <xmo+roboto@odoo.com> | 2018-11-23 17:04:50 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-11-23 17:04:50 +0100 |
| commit | df1fea4de1c629b3d9c8951a6cd4836d9d4ee0a3 (patch) | |
| tree | 825e9a30b7d27bc8bfb5af079f6f72eb16722b5e /addons/web/static/tests/fields/basic_fields_tests.js | |
| parent | cd2637cfdf0ec2c5dc2fa2b74b29fdffac822e87 (diff) | |
| parent | 55073e3baa97fa1285695233f30044bd7c698858 (diff) | |
[FIX] web_unsplash: new guidelines negociated with Unsplash
Unsplash CEO asked us to stop exposing our key client side (even if it was
only in the browser network and previously allowed by their API team leader).
Also, all our Odoo instances (on premise or not) should share the same
production key, which is not possible in our case obviously.
After multiple exchange, it has been negociated that:
1. Our non saas user won't be able to apply for a production key and should
prefix they Unsplash application name by 'Odoo:'. Their key will remain in
test mode.
Indeed, Unsplash won't be able to review every Odoo application and ensure
it respects the API terms and it is a real application.
2. Our saas user will query Unsplash server side so the key remain hidden.
3. The documentation should explain it all
task-1911345
closes odoo/odoo#28804
Diffstat (limited to 'addons/web/static/tests/fields/basic_fields_tests.js')
0 files changed, 0 insertions, 0 deletions
