Warn reader about risks of leaving NEW MASTER KEY REGISTER in Full Uncommitted state

[ibm-cloud-docs]

Warn reader about risks of leaving NEW MASTER KEY REGISTER in Full Uncommitted state

[silliman]

Since this situation can occur long after the service instance is initialized, I would suggest to change 'and' to 'or', that is,

Otherwise, you will not be able to initialize your service instance or perform cryptographic operations with GREP11 API or PKCS #11 API

[liuxjep]

@silliman Hi Barry. Thanks for the suggestion. I have added the following note at the beginning of the step 6:

Please check it out at: https://test.cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-hsm#step6-commit-master-key and let me know whether you have further comments. Thanks.

[silliman]

This is good, but, at least for the GREP11 API, leaving the NEW MASTER KEY register in "full uncommited" state also makes the "CURRENT MASTER KEY" unusable for most operations, so this impacts usage of the service even after the service instance is initialized.

[liuxjep]

@silliman so can I say like this: Otherwise, you will not be able to initialize your service instance and perform cryptographic operations with GREP11 API or PKCS #11 API.?

[liuxjep]

@silliman Updated. Thanks!