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
Related to #9289, after a method is invoked, authorization needs to know the object returned from the method invocation.
Because method invocations happen frequently, it's better to not create a new context object to hold both the MethodInvocation and the returned value. A new interface will allow for the return value to be passed in as a separate parameter instead.
Note that this is similar to AfterInvocationManager, though following AuthorizationManager's design, which allows for returning a decision instead of throwing an exception.
The text was updated successfully, but these errors were encountered:
- Removes the need to keep MethodAuthorizationContext#returnObject
in sync with other method parameters
- Restores MethodAuthorizationContext's immutability
Closesspring-projectsgh-9591
akohli96
pushed a commit
to akohli96/spring-security
that referenced
this issue
Aug 25, 2021
- Removes the need to keep MethodAuthorizationContext#returnObject
in sync with other method parameters
- Restores MethodAuthorizationContext's immutability
Closesspring-projectsgh-9591
Related to #9289, after a method is invoked, authorization needs to know the object returned from the method invocation.
Because method invocations happen frequently, it's better to not create a new context object to hold both the
MethodInvocation
and the returned value. A new interface will allow for the return value to be passed in as a separate parameter instead.Note that this is similar to
AfterInvocationManager
, though followingAuthorizationManager
's design, which allows for returning a decision instead of throwing an exception.The text was updated successfully, but these errors were encountered: