You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to remove this need, either by scanning the classpath for @AuthorizeReturnObject usage and/or by introducing an API where security-specific proxy hints can be specified.
Some things that should be considered:
Adding a Data-specific AotProcessor that inspects the generic types for beans of type RepositoryFactoryBeanSupport that use @AuthorizeReturnObject
Adding an AotProcessor that inspects the return values of bean methods that use @AuthorizeReturnObject, traversing the return type's object graph for any nested authorized return objects
Adding a way to directly indicate non-bean types that Security should proxy
The text was updated successfully, but these errors were encountered:
Related to #14652
Native applications currently need to manually register their authorization proxy classes using a
BeanFactoryInitializationAotProcessor
like so:It would be nice to remove this need, either by scanning the classpath for
@AuthorizeReturnObject
usage and/or by introducing an API where security-specific proxy hints can be specified.Some things that should be considered:
RepositoryFactoryBeanSupport
that use@AuthorizeReturnObject
@AuthorizeReturnObject
, traversing the return type's object graph for any nested authorized return objectsThe text was updated successfully, but these errors were encountered: