Expectation for the Domino ID vault to store the ID File encryption strength.
1) When one updates security Policy Settings document as below example.
Security Settings==>Password Management==>Password Management Basics==>ID File Encryption Settings==>Mandated Encryption Standard==>"256 bit AES and SHA-512"
2) Policy is applied to an end user and he did changed his password for updating the Mandated Encryption Standard.
3) The ID vault sync is done so the new password is also updated to the Vault.
4) When now the same user configures notes client on a different system downloading the latest synced id file from the vault, the id file still shows the old Encryption Strength.
And the user is needed again to do a password reset for updating the ID encryption strength.
This is because the ID File encryption strength is not stored in the ID file in the Vault. It is considered a "local" id file setting.
Thus Customer would need to once change the local ID file password for the new encryption level to get updated.
This process appears to be complicated and does not seem to me to be easily applicable, when clients use NSL.
Expectation is to have the encryption strength of the ID file to be applied by policy at least when the ID is downloaded from the IDVault after first password change and encryption strength update.
This idea is declared as shipped because the default IDFile encryption strength was updated in the Notes client v14.0
Please note that the IDFile encryption strength is not realted to how it is stored in the IDVault