root
/
spring-security
mirror of https://github.com/spring-projects/spring-security.git
1
0
Fork 0
Code Issues Actions 6 Packages Projects Releases Wiki Activity

doc: added hint to declare GrantedAuthorityDefaults as infrastructure bean 

Closes gh-14779
This commit is contained in:
Patrick Schmidt 2024-03-19 08:19:35 -03:00 committed by Marcus Hert Da Coregio
parent 09198447af
commit 1ebd663253
2 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/modules/ROOT/pages/reactive/authorization/method.adoc
View File

@ -105,6 +105,7 @@ Java::
[source,java,role="primary"] [source,java,role="primary"]
---- ----
@Bean @Bean
@Role(BeanDefinition.ROLE_INFRASTRUCTURE)
static GrantedAuthorityDefaults grantedAuthorityDefaults() { static GrantedAuthorityDefaults grantedAuthorityDefaults() {
return new GrantedAuthorityDefaults("MYPREFIX_"); return new GrantedAuthorityDefaults("MYPREFIX_");
} }
@ -113,7 +114,8 @@ static GrantedAuthorityDefaults grantedAuthorityDefaults() {
[TIP] [TIP]
==== ====
We expose `GrantedAuthorityDefaults` using a `static` method to ensure that Spring publishes it before it initializes Spring Security's method security `@Configuration` classes We expose `GrantedAuthorityDefaults` using a `static` method to ensure that Spring publishes it before it initializes Spring Security's method security `@Configuration` classes.
Since the `GrantedAuthorityDefaults` bean is part of internal workings of Spring Security, we should also expose it as an infrastructural bean effectively avoiding some warnings related to bean post-processing (see https://github.com/spring-projects/spring-security/issues/14751[gh-14751]).
==== ====
[[jc-reactive-method-security-custom-authorization-manager]] [[jc-reactive-method-security-custom-authorization-manager]]

5
docs/modules/ROOT/pages/servlet/authorization/method-security.adoc
View File

@ -234,6 +234,7 @@ Java::
[source,java,role="primary"] [source,java,role="primary"]
---- ----
@Bean @Bean
@Role(BeanDefinition.ROLE_INFRASTRUCTURE)
static GrantedAuthorityDefaults grantedAuthorityDefaults() { static GrantedAuthorityDefaults grantedAuthorityDefaults() {
return new GrantedAuthorityDefaults("MYPREFIX_"); return new GrantedAuthorityDefaults("MYPREFIX_");
} }
@ -245,6 +246,7 @@ Kotlin::
---- ----
companion object { companion object {
@Bean @Bean
@Role(BeanDefinition.ROLE_INFRASTRUCTURE)
fun grantedAuthorityDefaults() : GrantedAuthorityDefaults { fun grantedAuthorityDefaults() : GrantedAuthorityDefaults {
return GrantedAuthorityDefaults("MYPREFIX_"); return GrantedAuthorityDefaults("MYPREFIX_");
} }
@ -265,7 +267,8 @@ Xml::
[TIP] [TIP]
==== ====
We expose `GrantedAuthorityDefaults` using a `static` method to ensure that Spring publishes it before it initializes Spring Security's method security `@Configuration` classes We expose `GrantedAuthorityDefaults` using a `static` method to ensure that Spring publishes it before it initializes Spring Security's method security `@Configuration` classes.
Since the `GrantedAuthorityDefaults` bean is part of internal workings of Spring Security, we should also expose it as an infrastructural bean effectively avoiding some warnings related to bean post-processing (see https://github.com/spring-projects/spring-security/issues/14751[gh-14751]).
==== ====
[[jc-method-security-custom-authorization-manager]] [[jc-method-security-custom-authorization-manager]]