[JAMES-3040] LinShare blob export mechanism should rely on delegation

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Assignee: Unassigned
• Reporter: Nguyễn Việt Đức
• Created: 06/Feb/20 11:03
• Updated: 14/Feb/20 06:03
• Resolved: 14/Feb/20 06:03

Description

1. Description

Currently, James allows exporting the content of a blob via LinShare.

To do so, we rely on an administrator account that upload & share

1. Current behaviour

To do so, we rely on an administrator account that upload & share the blob to the end user.

1. Expected result

We should rather rely on "delegation APIs" to do so.

Reuse output of this in your tests...

Configuration inludes (k8s injected) technical user + passwd, James relies on simple auth mechanism upon each request.

1. Requirements:

• A delegation account including (uuid/password)

1. Steps:

• Get target user uuid (blobs will be uploaded to this user's spaces). For example: [e-mail]

  GET http://localhost:28080/linshare/webservice/rest/delegation/v2/users/{target-user-mail}
  -u "delegation-account-uuid:delegation-account-password"
  
  200: Ok, created
  Not 200: Bad result
  

Response body:

{
    "uuid": "b3684f3c-f239-4826-9dcc-0731f933c6ef",
    "domain": "e57bb7b8-77b5-4d12-b6bb-a3f6894fcf5f",
    "firstName": "John",
    "lastName": "Doe",
    "mail": "[e-mail]",
    "accountType": "INTERNAL",
    "external": false
}

1. Upload directly to user space `My Space`).

Easy, but files structure in user spaces will be messy, an exported blob will be in the same place with bunch of files that users will be uploading.

POST localhost:28080/linshare/webservice/rest/delegation/v2/{target-user-uuid}/documents
-u "delegation-account-uuid:delegation-account-password"

200: Ok, created
Not 200: Bad result