key rollover when keyname present

[Alan Buxey]

the current keyname is in place because of hard-coded usage of it
within the config.... that usage including signing and encryption.
would using a Chaining definition
work for this eg

<CredentialResolver type="Chaining" keyname="live">
     <CredentialResolver type="File" key="new-sp.key"
certificate="new-sp.crt" use="signing"/>
     <CredentialResolver type="File" key="sp.key" certificate="sp.crt"/>
</CredentialResolver>

I'm thinking not because of the relying-party hard set with encryption
and signing for that keyname.....  hmmm.  I note the documentation
covering the keyname says
"Primarily used to allow different keys and certificates to be used
based on the identity provider. While this works in some situations,
it can be complex to get working, and it's strongly advisable for SPs
to maintain a single set of credentials to use for all interactions."
- may have to add key rollover issues to that caveat ;-)

alan