Skip to content

(#407) Added docs warning about data leakage prevention. #442

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.

Sign up for GitHub

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

Merged
adrianhall merged 1 commit into from
Feb 16, 2026
Merged

(#407) Added docs warning about data leakage prevention. #442

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions docs/in-depth/server/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -200,6 +200,11 @@ To use this access control provider, update your `TableController` as follows:

If you want to allow both unauthenticated and authenticated access to a table, decorate the controller with `[AllowAnonymous]` instead of `[Authorize]`.

!!! warning
It is very easy to accidentally leak data for a different user when using access control providers to limit the data. If the operation is create and the entity that exists is for another user, the response will contain the information for the other user.

To prevent this data leakage case, it is important to add a filtering that ensures the data being returned is for the same user.

## Configure logging

Logging is handled through [the normal logging mechanism](https://learn.microsoft.com/aspnet/core/fundamentals/logging/?view=aspnetcore-10.0) for ASP.NET Core. Assign the `ILogger` object to the `Logger` property:
Expand Down