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

Create a private test index with semantic capability in azure-db #19

Open
2 of 6 tasks
Tracked by #108
k-allagbe opened this issue May 6, 2024 · 0 comments
Open
2 of 6 tasks
Tracked by #108
Assignees

Comments

@k-allagbe
Copy link
Member

k-allagbe commented May 6, 2024

Description

The goal is to set up a private test index in Azure Search with semantic capabilities. This index should ensure that only clients on our private network have access to private documents.

Tasks

  • Create a new index in Azure Search with semantic capabilities.
  • Configure security settings to restrict access to the new index. #20
  • Populate the index with sample private documents.
  • Implement tests to verify that only private finesse can access the documents. (Manual test)
  • Document the setup and configuration steps.
  • Review and validate the security measures in place.

Acceptance Criteria

  • A new semantic index is successfully created in Azure Search.
  • Access to the index is limited to the specified private clients.
  • Security tests confirm that no unauthorized access is possible.
  • Documentation is complete and accurate.
@k-allagbe k-allagbe transferred this issue from ai-cfia/finesse-frontend May 6, 2024
@k-allagbe k-allagbe changed the title A new private index on top of fake private documents Create a test private index with semantic capability in azure-db May 6, 2024
@k-allagbe k-allagbe changed the title Create a test private index with semantic capability in azure-db Create a private test index with semantic capability in azure-db May 6, 2024
@k-allagbe k-allagbe added this to Finesse May 6, 2024
@k-allagbe k-allagbe moved this to Todo in Finesse May 6, 2024
@k-allagbe k-allagbe closed this as not planned Won't fix, can't repro, duplicate, stale May 9, 2024
@github-project-automation github-project-automation bot moved this from Todo to Done in Finesse May 9, 2024
@k-allagbe k-allagbe reopened this May 13, 2024
@k-allagbe k-allagbe moved this from Done to Todo in Finesse May 15, 2024
@ibrahim-kabir ibrahim-kabir self-assigned this May 15, 2024
@ibrahim-kabir ibrahim-kabir moved this from Todo to In Progress in Finesse May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

No branches or pull requests

2 participants