In preparing a doc patch for
OPENIG-365, I noticed that baseURI (in several places) and redirectURI (in the SamlFederationHandler) take strings at present rather than expressions.
This means that two protect a couple of applications with OpenIG as SAML 2.0 SP, I end up with Route configurations that are almost duplicates, but not quite.
If these fields could take expressions, rather than strings, I could parameterize them and avoid copy/paste errors.
My guess is that we will discover more use cases where string values are too inflexible, so it would be nice to review fields that take string values today and consider making more of them expressions instead.