Splitting the relying-party.xml
kwessel at illinois.edu
Tue Aug 25 17:13:18 UTC 2020
I'm wanting to split our relying-party.xml into multiple files for easier merging between test and prod environments. Essentially, I want to put my relying party overrides list into a separate file, wrapped in its own <beans> block, of course. I could then include it either by adding it as a resource to the relying party resolver bean in services.xml or as a <import> element in relying-party.xml. End result: I could have different overrides in test vs. prod while still having the same base configuration in both environments.
1. Is this split going to work, or does that overrides bean need to be in the file where the unverified and default RP configurations are defined?
2. Is there any reason I should choose the <import> method vs. adding it as a resource to services.xml?
More information about the users