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

Plan for access control architecture #203

Open
1 of 4 tasks
kislyuk opened this issue Jun 21, 2019 · 1 comment
Open
1 of 4 tasks

Plan for access control architecture #203

kislyuk opened this issue Jun 21, 2019 · 1 comment
Labels

Comments

@kislyuk
Copy link
Member

kislyuk commented Jun 21, 2019

Steps:

  • De-risk jointly with DSS the granularity of authorization scopes (e.g. will access control apply per environment, per zone, per bundle, or other)
  • Implement DCP standard authn in the dcpquery frontend
  • Decide how to apply authorization scopes to query results, and if any schema changes are necessary to accommodate this
  • Implement DCP standard authz in the dcpquery frontend
@mweiden mweiden added the spike label Aug 6, 2019
@mweiden mweiden added this to the Q3 2019 Milestone 3 milestone Aug 6, 2019
@mweiden
Copy link
Collaborator

mweiden commented Oct 8, 2019

@MDunitz have a discussion with Trent and make sure your project_files join table (for supporting an ACL) makes sense with his Authorization design. Document the plan here and then close this.

@mweiden mweiden removed this from the Q3 2019 Milestone 3 milestone Nov 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants