Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implementation of a service to take registration requests #1

Open
constantinius opened this issue Dec 7, 2020 · 1 comment
Open

Comments

@constantinius
Copy link
Contributor

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).

@Schpidi
Copy link
Collaborator

Schpidi commented Apr 16, 2021

I believe this is done right @constantinius? Could you link to the PR and close this? Thx

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants