Skip to content

Implementation of a service to take registration requests #1

@constantinius

Description

@constantinius

This service shall have two routes:

  • User information: when called with user credentials encoded in a JWT, this endpoint shall return the Object Storage endpoint, bucket (or container name) and path the processor can place its files. As the integration with the PEP/PDP (user authorization) is not yet understood, this needs to be mocked to a single bucket + path prefix.
  • Registration: this route shall take the prefix of data to be registered into the data-access component. Again, the users credentials are passed via a JWT. The path shall be placed into the redis registration_queue of the VS

This service shall be implemented by the means of any Python web framework (suggestion: Flask).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions