Annotation Type EnableMethodSecurity
-
@Retention(RUNTIME) @Target(TYPE) @Documented @Import(org.springframework.security.config.annotation.method.configuration.MethodSecuritySelector.class) @Configuration public @interface EnableMethodSecurity
Enables Spring Security Method Security.- Since:
- 5.6
-
-
Optional Element Summary
Optional Elements Modifier and Type Optional Element Description boolean
jsr250Enabled
Determines if JSR-250 annotations should be enabled.org.springframework.context.annotation.AdviceMode
mode
Indicate how security advice should be applied.boolean
prePostEnabled
Determines if Spring Security'sPreAuthorize
,PostAuthorize
,PreFilter
, andPostFilter
annotations should be enabled.boolean
proxyTargetClass
Indicate whether subclass-based (CGLIB) proxies are to be created as opposed to standard Java interface-based proxies.boolean
securedEnabled
Determines if Spring Security'sSecured
annotation should be enabled.
-
-
-
Element Detail
-
prePostEnabled
boolean prePostEnabled
Determines if Spring Security'sPreAuthorize
,PostAuthorize
,PreFilter
, andPostFilter
annotations should be enabled. Default is true.- Returns:
- true if pre/post annotations should be enabled false otherwise
- Default:
- true
-
-
-
proxyTargetClass
boolean proxyTargetClass
Indicate whether subclass-based (CGLIB) proxies are to be created as opposed to standard Java interface-based proxies. The default isfalse
. Applicable only ifmode()
is set toAdviceMode.PROXY
.Note that setting this attribute to
true
will affect all Spring-managed beans requiring proxying, not just those marked with@Cacheable
. For example, other beans marked with Spring's@Transactional
annotation will be upgraded to subclass proxying at the same time. This approach has no negative impact in practice unless one is explicitly expecting one type of proxy vs another, e.g. in tests.- Returns:
- true if subclass-based (CGLIB) proxies are to be created
- Default:
- false
-
-