In the vault limitations, we can read that Smartcard-enabled IDs cannot be stored in a vault. A new user ID, which has not been smartcard-enabled yet, is loaded into the vault. If the user ID is smartcard-enabled after the initial vault upload, what happens if a rename, recertification or key rollover is done? Do we need to disable the smartcard protection and enable it after the action?
Feedback response number TKLR8UCGTZ created by Thorsten Klauser on 05/16/2012