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

Clarify DB security requirements #60

Open
mcupak opened this issue Nov 25, 2020 · 0 comments
Open

Clarify DB security requirements #60

mcupak opened this issue Nov 25, 2020 · 0 comments
Labels
prc Product review committee request task Question or task not requiring code changes

Comments

@mcupak
Copy link
Collaborator

mcupak commented Nov 25, 2020

In the docs and PRC report:

Using Search to give low-level access to a database as a data layer for high-level tools is only going to be scalable (in terms of number of high-level tools)and only feasible for federation atop if database security is handled at low levels, and is not the responsibility of each of the high-level services atop. What is the security model for, e.g., the database contains data from multiple datasets only one of which the requester has access to? How is that handled by a Search implementation? Needs clarification.

@mcupak mcupak added task Question or task not requiring code changes prc Product review committee request labels Nov 25, 2020
@mcupak mcupak added this to the 1.0.0 milestone Nov 25, 2020
@mcupak mcupak modified the milestones: 1.0.0, 1.1.0 Apr 14, 2021
@mcupak mcupak removed this from the 1.1.0 milestone May 26, 2021
@mcupak mcupak added this to the 1.1.0 milestone Jun 9, 2021
@mcupak mcupak removed this from the 1.1.0 milestone Dec 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
prc Product review committee request task Question or task not requiring code changes
Projects
None yet
Development

No branches or pull requests

1 participant