Follow up doc items after BYOK release

[jacobwdv]

Docs : https://openliberty.io/docs/latest/bring-your-own-aes-256-key.html

Blog: https://blogs-draft-openlibertyio.mqj6zf7jocq.us-south.codeengine.appdomain.cloud/blog/2025/12/02/25.0.0.12.html#aes256

Before GA we updated the Blog with examples and verbiage that we preferred such as 'Obtain a 256-bit AES key' instead of 'Generate' in step 1.

We would like the blog post and docs for 'bring your own AES-256 key for liberty passwords' to be in sync because we preferred the language used in the blog post.

Note, the docs topic has more content, that looks fine to us, we just want the examples and text up until the note about 'for best performance' to be synchronized.

Also, we would like to have the BYOK section referenced in: https://openliberty.io/docs/latest/password-encryption.html

[jacobwdv]

This is follow up work from: #8021

[ramkumar-k-9286]

Hi Jacob @jacobwdv

The suggested corrections to the language were made to the page, to ensure 'sync' with the blog page.

Draft link: https://docs-draft-openlibertyio.mqj6zf7jocq.us-south.codeengine.appdomain.cloud/docs/latest/bring-your-own-aes-256-key.html

Reference link added in "See also": Draft link: https://docs-draft-openlibertyio.mqj6zf7jocq.us-south.codeengine.appdomain.cloud/docs/latest/password-encryption.html

Please add the Developer Reviewed label if you are satisfied with the changes.

Regards,
Ramkumar.

[jacobwdv]

Hello @ramkumar-k-9286

I quickly looked at the Draft link: https://docs-draft-openlibertyio.mqj6zf7jocq.us-south.codeengine.appdomain.cloud/docs/latest/bring-your-own-aes-256-key.html

and compared it to the blog post: https://blogs-draft-openlibertyio.mqj6zf7jocq.us-south.codeengine.appdomain.cloud/blog/2025/12/02/25.0.0.12.html#aes256

It don't see them matching. Obtain a 256-bit AES Key section, for example, doesn't have the new examples or verbiage guiding users how to use it. There are still 3 examples instead of 4.

Can you please take a look?

[jacobwdv]

Also, I noticed openlIberty.io has securityUtility commands page, the landing page has the generateAESKey action but the menu on the left is missing it. can you fix that?

[ramkumar-k-9286]

Yes, the TOC navigation for generateAESKey has been fixed in the draft and staging sites. Will be updated in the 26.0.0.1 release.

Staging site: https://docs-staging-openlibertyio.mqj6zf7jocq.us-south.codeengine.appdomain.cloud/docs/latest/reference/command/securityUtility-commands.html

Please add the Developer Reviewed label if you are satisfied with the changes.

[ramkumar-k-9286]

Hi Jacob @jacobwdv

Draft link: https://docs-draft-openlibertyio.mqj6zf7jocq.us-south.codeengine.appdomain.cloud/docs/latest/bring-your-own-aes-256-key.html

Regards,
Ramkumar

[jacobwdv]

Performance Tip: For best performance, re-encrypt all passwords by using the new AES-256 key. Open Liberty supports older password formats, but full migration provides consistent startup performance.

the green TIP box says TIPTIP

there are 4 examples in the blog post and only 3 in the docs. Could we copy all the syntax from the blog?

To generate a 256-bit AES key using securityUtility, run the new securityUtility generateAESKey task to:

    Generate a random AES key:

    ./securityUtility generateAESKey

    Optionally, save a random AES key to an XML file:

      securityUtility generateAESKey --createConfigFile=myAesConfig.xml

    Or, generate a non-random AES key from a passphrase:

    ./securityUtility generateAESKey --key=<password>

    Optionally, generate a non-random AES key from a passphrase and save it into an XML file:

      securityUtility generateAESKey --key=<password> --createConfigFile=myAesConfig.xml