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

Identity acceptable risks and a mitigation designs for protecting index metadata #31

Open
jpnavarro opened this issue Feb 17, 2025 · 1 comment
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@jpnavarro
Copy link
Collaborator

jpnavarro commented Feb 17, 2025

A single consolidated Globus search index with multiple publishers introduces the possibility that publishers may corrupt or delete metadata they don't own. The risk and possible mitigation designs need to be explored, and a decision made on which designs will be implemented.

@jpnavarro jpnavarro changed the title Identity acceptable risks and a mitigation designs for projecting index metadata Identity acceptable risks and a mitigation designs for protecting index metadata Feb 17, 2025
@jpnavarro jpnavarro marked this as a duplicate of #32 Feb 18, 2025
@jpnavarro
Copy link
Collaborator Author

jpnavarro commented Mar 12, 2025

The risk of accidental modification or deletion of index entries outside of each projects area was determined to significant enough to mitigate, especially since it can be addressed using the following design:

  • projects would only publish to project specific staging indexes
    -changes in staging indexes are propagated by a synchronizer component/service to the global index
  • propagate only the changes in each project staging index for that project (i.e. project staging index entries from a different project are ignore and don't affect the global index)
  • the synchronize can be configured with a policy to ignore deletions in the staging index and not propagate them (i.e. it doesn't look for global index entries missing in their project staging index or delete them)

See the design.md.

@jpnavarro jpnavarro added the documentation Improvements or additions to documentation label Mar 12, 2025
@jpnavarro jpnavarro self-assigned this Mar 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant