-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Others' documents being inferenced despite having set up the ACLs #2278
Comments
Here are some ideas for how to debug: When you look at the thought process for the answers, take note of the filter being sent to the search engine, and of the groups and oids that are attached to the search results. It should only find documents that match the filter. What are your values for these azd env variables?
Make sure those variables match what you want to happen: |
AZURE_ENFORCE_ACCESS_CONTROL is set to true and AZURE_ENABLE_ GLOBAL_DOCUMENT_ACCESS is false. That being said the filter hasn't been set to anything. It is transmitting the same OID for multiple people, is there something else we would need to change? |
Just making sure, you also have user login enabled, correct? The build_filter function should be building the filter based off the Entra OID of the currently logged in user. |
AZURE_USE_AUTHENTICATION is set to true...here are the .env variables (with our info redacted): AZURE_AUTH_TENANT_ID="###" Thank you for all your help! |
Our model still inferences others' documents despite having run the "python ./scripts/manageacl.py --acl-action enable_acls" command. Everything else is up and running, but we just realized it was still pulling documents from other users, so we guessed there was a problem with how the acls got setup. We looked through the documentation but it seems like after running that command the documents should be restricted...thank you for your help!
The text was updated successfully, but these errors were encountered: