feat: add initial support for restricted keys query provider implementation #274
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.
This PR adds support for row filtering via restricting query search criteria using pluggable RestrictedKeysProvider implementation.
The RestrictedKeysProvider functional interface should provide a list of restricted keys in order to filter records at runtime based on user security context and supplied EntityIntrospection descriptor arugment.
The return argument uses Optional<List> return type.
You can configure the implementation of the provider via
GraphqJpaSchemaBuilder.restrictedKeysProvider
builder method Java Api, i.e.,The provided
graphql-jpa-query-boot-starter
will detect and automatically inject RestrictedKeysProvider bean instance from application context.Fixes #219