Now that the trivial keymaster supports multiple keys, let's do
something similar for the KMIP keymaster. Additional keys are
configured as:
key_id_<secret_id> = <KMIP unique identifier>
While it might be tempting to use the unique identifier directly as the
secret_id, the added indirection allows operators to move keys between
different backends, which may cause different identifiers to be issued.
As with the trivial keymaster, the key to use for PUTs and POSTs is
specified with:
active_root_secret_id = <secret_id>
Change-Id: Ie52508e47d15ec5c4e96902d3c9f5f282d275683
0dc1b6250e