Hi Tamas,
Nice to meet you on this list :)
That indeed is the reason why the type-annotations were ignored and by
replacing the AuthorizationAttributeSourceAdvisor with a custom one I have
worked around the problem, but I am still wondering if this is the intended
behavior or this is a bug.
Basically this is the workaround:
override fun matches(method: Method, targetClass: Class<*>): Boolean
=
super.matches(method, targetClass)
|| securityAnnotations.any {
AnnotationUtils.findAnnotation(targetClass, it) != null }
and then one has to replace the AuthorizationAttributeSourceAdvisor in the
spring context.
Best regards,
Laszlo
