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

Private extractors #870

Open
lmarini opened this issue Jan 10, 2024 · 1 comment
Open

Private extractors #870

lmarini opened this issue Jan 10, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@lmarini
Copy link
Member

lmarini commented Jan 10, 2024

In v1 extractors can send user ids to backend and only those users can use them. Can we do the same in v2?

@lmarini lmarini added the enhancement New feature or request label Jan 10, 2024
@lmarini lmarini added this to the v2.1 milestone Jan 10, 2024
@max-zilla
Copy link
Contributor

A bit more detail on v1 implementation...
https://github.com/clowder-framework/clowder/pull/300/files
clowder-framework/pyclowder#39

  • PyClowder recognizes environment variables EXTRACTOR_KEY and CLOWDER_EMAIL. the unique_key is used in the name of the queue: self.rabbitmq_queue = "private.%s.%s" % (extractor_key, self.rabbitmq_queue). email is injected inot the heartbeat: 'owner': self.clowder_email,
  • The owner and unique_key are included in the extractor registration info in Clowder.
  • Any API requests involving extractors honor these. If you submit file 123 to extractor wordcount...
    • If you include a unique_key and it matches a private one assigned to you, submit to that one.
    • If no key, it will route to a normal (public) wordcount if available.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Todo
Status: No status
Development

No branches or pull requests

2 participants