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

Define Authentication/Authorization model. #12

Open
joerg84 opened this issue Jun 10, 2019 · 2 comments
Open

Define Authentication/Authorization model. #12

joerg84 opened this issue Jun 10, 2019 · 2 comments
Projects

Comments

@joerg84
Copy link
Contributor

joerg84 commented Jun 10, 2019

No description provided.

@joerg84 joerg84 added this to To do in Planning via automation Jun 10, 2019
@rajivsam
Copy link
Contributor

rajivsam commented Jun 12, 2019

  1. What does Arango UI use for authentication and authorization? Can we reuse that? If we could we probably have some in house experts who are familiar with it.
  2. Should we investigate an api like ambassador for this? (https://www.getambassador.io/user-guide/auth-tutorial/) or perhaps an OAuth2 provider?
  3. Defining the different roles and a mapping of roles to arangopipe API must be done. For the MVP, we could go with:
  • Data Scientist
  • Date Engineer
  • Application Administrator

@joerg84
Copy link
Contributor Author

joerg84 commented Jun 18, 2019

User Stories:

  • [optional ]Dan, the data scientist, wants to share meta-data about his projects with some colleagues but not all.
  • [MVP] Jim, a Arangopipe admimistrator, needs to provision projects to be tracked by Arangopipe.
  • [Optional] John, a data engineer, wants to share meta-data about his projects with some colleagues but not all.
  • John, the data engineer, develops some feature set generating pipelines. He wants to make sure that only he or some of his colleagues can log metadata information about these pipelines with Arangopipe.
  • Dan, the data scientist, develops some modeling pipelines. These pipelines will create machine learning metadata like model parameters and model hyper-parameters. He wants to make sure that only he or some of his colleagues can log metadata generated by modeling pipeline execution with Arangopipe.
  • Harvey, the dev-ops engineer often needs details about feature set or modelling pipelines. He is not going to be creating meta-data, he just needs to view them when he needs the information.
  • [MVP] Jim needs to provision users like Dan, John or Harvey into Arangopipe.

MVP
Private/Public
Roles: Admin, Data Engineer, Data Scientist
At MVP no further distinction between individuals inside a role

Note: The following talk seems to give one example of how data scientists could collaborate
https://www.youtube.com/watch?v=kExwqij11cg

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

No branches or pull requests

2 participants