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
Describe the bug
When declaring a relying-party-registration element in a Spring Security XML namespace configuration, attributes having a property-placeholder value (e.g. ${...}) are not resolved, even when property-placeholder configuration is declared.
Expected behavior
The property-placeholders are resolved when the Spring context is created (ref. #14645).
The Spring Framework documentation mentions that adding PropertySources to the Environment is only required in case of modularization of properties. In this example this is not the case is it?
By researching the PropertySourcesPlaceholderConfigurer source code, it does not actually add properties directly to the Environment. Instead, after the instance is created, it invkoe the postProcessBeanFactory method, where it adds the property source and the current Environment as two property sources and calls addEmbeddedValueResolver to add it to the IOC container as a placeholder resolver. Therefore, when parsing and loading BeanDefinition during XML parsing, there are only two property sources in Environment: systemEnvironment and systemProperties
Describe the bug
When declaring a
relying-party-registration
element in a Spring Security XML namespace configuration, attributes having a property-placeholder value (e.g.${...}
) are not resolved, even whenproperty-placeholder
configuration is declared.Expected behavior
The property-placeholders are resolved when the Spring context is created (ref. #14645).
Sample
demo.zip
Versions:
The text was updated successfully, but these errors were encountered: