[EXTDAM-160] Respect public/private notion of Bynder images Created: 06/Oct/20  Updated: 21/Dec/20  Resolved: 09/Dec/20

Status: Closed
Project: External DAMs
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0.4

Type: Story Priority: Neutral
Reporter: Ilgun Ilgun Assignee: Rabie Hayoun
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 2.5h
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Documentation update required:
Yes
Date of First Response:
Epic Link: DAM Phase 2
Sprint: Add-Ons 49, Add-Ons 50, Add-Ons 51, Add-Ons 52, Add-Ons 53
Story Points: 8

 Description   

Bynder provides private/public images. They differentiate it using 'originalURL' which is in the response when an image is set to be public.

Therefore, we need to use that image whenever we render a Bynder image e.g. in pages app.

 

AC

  • Make sure whenever we distribute Bynder image, we use original URL.


 Comments   
Comment by Rabie Hayoun [ 27/Nov/20 ]

As part of this ticket, we have 2 ways to render(URL generation) bynder asset based on a configuration parameter for the BynderAssetRenderer class. the parameter is called "proxyMode".

Behavior:

  1. When proxy mode is on (true), the bynder asset will generate a magnolia URL to hyde bynder URLs and the Assets will be served through Magnolia instance.
  2. When proxy mode is off (false), the bynder asset will generate a bynder URL and will be served directly by Bynder.
Generated at Mon Feb 12 01:52:29 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.