I use XML based configuration for most security setup as I have customisations that need to be dynamically processed.
Using <security:relying-party-registration... Everything works fine if I hardcode the metadata-location and assertion-consumer-service-location but using a propertyConfigurer the values aren't used.
Using Spring Security 6.0.8
I use XML based configuration for most security setup as I have customisations that need to be dynamically processed.
Using <security:relying-party-registration... Everything works fine if I hardcode the metadata-location and assertion-consumer-service-location but using a propertyConfigurer the values aren't used.
I have this setup for the propertyConfigurer
<context:property-placeholder location="file:${application.properties}"/>
application.properties contains these values:
relying-party-registrations is setup like this:
Values are not propagated in the relying-party-registration.