Ticket #521 (closed defect: fixed)

Opened 2 years ago

Last modified 21 months ago

<is_protected> is not filled correctly

Reported by: Michiel.Schok Owned by: forgacs
Priority: critical Milestone: MediaMosa 3.0
Component: Core Version:
Keywords: Cc:
MoSCoW: none Estimated time after impact analysis:
Related to project: none Tested: no
Accepted: no Estimated Hours: 0

Description

In the SURFmedia workflow, the user can define an ACL during upload. This ACL is implemented immediately after creating the mediafile.
See for instance asset 'DXfTvKKaGUNLbkaUq3wmjLgD', mediafile 'C2UjEEtVYYNJQ7CMFQ7uV6lT' on VP-Core acceptatie.

<request_uri>[GET] mediafile/C2UjEEtVYYNJQ7CMFQ7uV6lT/acl?user_id=urn:collab:person:surfnet.nl:michiel</request_uri>

  <items>
    <item>
      <aut_realm>michiel@schok.net</aut_realm>
    </item>
  </items>

But when we request the asset, we observe that 'granted' and 'protected' are not filled with the correct values.

<request_uri>[GET] asset/DXfTvKKaGUNLbkaUq3wmjLgD</request_uri>

<items>
    <item>
      <asset_id>DXfTvKKaGUNLbkaUq3wmjLgD</asset_id>
      <app_id>5</app_id>
...
      <is_protected>FALSE</is_protected>
...
      <granted>TRUE</granted>

Change History

Changed 2 years ago by forgacs

  • owner set to forgacs
  • status changed from new to assigned

Changed 2 years ago by forgacs

  • status changed from assigned to closed
  • resolution set to fixed

It is fixed in the latest version of MediaMosa.

Changed 21 months ago by forgacs

  • status changed from closed to reopened
  • resolution fixed deleted

I reopened this ticket. When we tested this issue we found a bug in the code. We will create a new build with this fix later.

A little note about the "is_protected" fields: We have two "is_protected" fields. One for assets and one for mediafiles. The asset "is_protected" field is related to the asset ACL layer and that is not ready. The mediafile "is_protected" field is set correctly according to the mediafile ACL layer.

Changed 21 months ago by Michiel.Schok

When testing the MediaMosa 3.0.3. release (VP-Core acceptance) with SURFmedia 3.1, this bug is nagging us.

SURFmedia doesn't use the <is_protected> fields for an asset or mediafile, but instead relies on the <granted> field that is returned from VP-Core.

If <granted> is filled with TRUE, SURFmedia shows 'stills', 'possibilites to play' the video, etc.
If <granted> is filled with FALSE, SURFmedia shows a 'lock' icon, and no possibilities to play the video.

At the moment, I observe that for asset_ids T1rqDWuN5BIHdJMEVFtASoCp, W1bStWoDaVIGSaYfKZ3ZJxjr and y1OFUTFjNqSROa9jKHJ4DoMY the <GRANTED> field is filled with TRUE where it should be FALSE according to the ACL.

Changed 21 months ago by Frans

  • priority changed from major to critical

Peter, can you have a look at this one and give us an estimate for fixing this?

Changed 21 months ago by forgacs

Frans, Michiel,
We have found a bug in the code earlier related to this issue. You can see my previous comment about it. This is the reason I deleted the "fixed" flag from this ticket.
The bug was fixed that time, and we will create a new build soon with the other fixes together.
Please wait till we release this new build.

Changed 21 months ago by forgacs

  • status changed from reopened to closed
  • resolution set to fixed

This ticket is fixed, and the new debian package was created.
You can test this issue after the release of MediaMosa 3.0.4 to acceptation.

Note: See TracTickets for help on using tickets.