...
consumed in a builder as a (Spring) Resource where it is then converted and passed on as a X509Certificate
(Q: So this is also Converted by spring (via FilesystemGenericApplicationContext), or is this distinct as a behavior?)
ResourceBackedMetadataProvider <HttpResource>
...
Unsupported. Fails during parsing
ResourceBackedMetadataProvider ResourceBackedMetadataProvider < Any> <PropertyReplacement>
...
RelyingParty
N/A - this will be deprecated removed in V4
Resource
Use Used in the security schema for TrustEngines and for the {{the ResourceBackedMetadataProvider}}
Security
X509Filesystem
<Certificate>, <PrivateKey>., <CRL> all take a string
Consumed in a builder as a Resource (i.e. converted by spring via FilesystemGenericApplicationContext ) and converted and passed on as javax.security.PrivateKey, ava.security.cert.X509Certificate, java.security.cert.CRL
...
<SecretKey>, <PrivateKey>., <PublicKey> : all take a string
...
Can we jettison this? At the very least we can get rid of all the unused types. Note that jettisoning this means doing as good a job with its replacement as we currently do for relying party. Note this gets used in the attribute resolver to define LDAP security behavior.
Resource Schema
With the security schema gone this is only ever used in the ReourceBackedMetadataProvider. I suggest that we only support (the existing) resource-ref="beanId", although we could add
...