Address filter access deny issue for Cosmos #1436
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why make this change?
operationToColumnMap.Excluded
andoperationToColumnMap.Included
and by introducing field level auth check into theGQLFilterParser
recent update results the issue that we are seeing.CosmosMetadataProvider
does not translate a field wild card (*) or list of hardcoded include columns to the list of AllowedFields in the engine'sAuthorizationResolver
currently, but we can add a pass through to theTryGetExposedColumnName
as suggested so it doesn't throw aNotImplementedException
when user accidently passed in the fields settings in the Cosmos configuration file.What is this change?
How was this tested?
Sample Request(s)