Open GoogleCodeExporter opened 9 years ago
PKCS11KeyStoreKeyingDataProvider initializes a KeyStore based on a provider
configured with the slot. Changing the slot would require to reconfigure the
KeyStore and would probably be an explicit operation (dedicated method). None
of this is currently supported, i.e. a PKCS11KeyStoreKeyingDataProvider
instance will only work with a given slot.
You probably could implement a KeyingDataProvider which is a composite around
multiple PKCS11KeyStoreKeyingDataProvider, each one configured for its own
slot.
Another option is to redefine the KeyingDataProvider on the profile and use a
new signer on each operation. This one sounds worst.
Original comment by luis.fgoncalv
on 11 May 2014 at 9:58
Any comments?
Original comment by luis.fgoncalv
on 13 May 2014 at 8:05
Original issue reported on code.google.com by
hak...@gmail.com
on 1 May 2014 at 7:55