Skip to content

Refactor certificate documentation - bring your own key ring#4903

Open
MarkAckert wants to merge 27 commits intodocs-stagingfrom
user/markackert/cert-scenarios
Open

Refactor certificate documentation - bring your own key ring#4903
MarkAckert wants to merge 27 commits intodocs-stagingfrom
user/markackert/cert-scenarios

Conversation

@MarkAckert
Copy link
Member

@MarkAckert MarkAckert commented Jan 23, 2026

As part of the work we're doing in zowe/zowe-install-packaging#4238 and zowe/zowe-install-packaging#4652 for Zowe 3.5.0, we're refactoring documentation to lead users towards bringing their own certificates and key rings to Zowe, rather than leading them to running through our init certificate tool. As part of this work, I took the opportunity to re-organize some of the certificate documentation with the following goals:

  • Reduce redundant or duplicated content across different pages
  • Simplify the "flow" through the documentation - fewer circular references, and simpler, streamlined choices at the end of certain articles
    • Additionally changed the sidebar organization to reflect this. Root article -> 2 sub-folders and "Finalize Configuration".
  • Remove some unnecessary or outdated information (e.g. Java 8 note, and why we need "password" with key rings in Java - it's good for devs to know, but in this case users should focus on ensuring the right configuration is in place, not necessarily why it needs to be there).

Still to do:

  • Review from SMEs 😄

Signed-off-by: MarkAckert <35308966+MarkAckert@users.noreply.github.com>
Signed-off-by: MarkAckert <35308966+MarkAckert@users.noreply.github.com>
@MarkAckert MarkAckert added area: install and config Issues related to z/OS install and config release: V3 Zowe V3 content review: doc Needs review by Doc Squad member review: sme Needs review by an SME labels Jan 23, 2026
@github-actions
Copy link

github-actions bot commented Jan 23, 2026

😺 Thank you for creating this PR! To publish your content to Zowe Docs, follow these required steps.

  • Add the label review: doc.
  • Identify your content topic with a label. (Examples: area: apiml, area: cli, area: install and config, etc.)
  • Specify the major Zowe release(s) for your content. (Examples: release: V1, release: V2, release: V3)
    • If adding content that needs to be removed from V3 documentation, add the V3 N/A tag.
  • Select the master branch if your PR updates content that is on the live site. Select docs-staging if your PR updates content for a future release.
  • Notify the Doc Squad about this PR. If you don't know whom should review your content, message the #zowe-doc Slack channel. If you know which Doc Squad writer should approve your content, add that person as a reviewer.

Need help? Contact the Doc Squad in the #zowe-doc Slack channel.

@github-actions
Copy link

📁 The PR description is missing the file name(s) for the updated content. List all the files included in this PR so this information displays in our Zowe Docs GitHub Slack channel.

If you have addressed this issue already, refresh this page in your browser to remove this comment.

Signed-off-by: MarkAckert <35308966+MarkAckert@users.noreply.github.com>
@github-actions
Copy link

github-actions bot commented Jan 23, 2026

@github-actions github-actions bot temporarily deployed to pull request January 23, 2026 16:38 Inactive
Copy link
Collaborator

@anaxceron anaxceron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lots of great doc, @MarkAckert, thank ya!

Left some comments, mostly about Zowe style. Some are suggestions/questions and not requests for edits, per se. You make the call.

Signed-off-by: Martin Zeithaml <66114686+Martin-Zeithaml@users.noreply.github.com>
@github-actions github-actions bot temporarily deployed to pull request January 26, 2026 09:12 Inactive
Corrected typos in the documentation regarding certificate labels and names.

Signed-off-by: Martin Zeithaml <66114686+Martin-Zeithaml@users.noreply.github.com>
@github-actions github-actions bot temporarily deployed to pull request January 26, 2026 13:07 Inactive
Fixed formatting issues in YAML examples and export messages.

Signed-off-by: Martin Zeithaml <66114686+Martin-Zeithaml@users.noreply.github.com>
@github-actions github-actions bot temporarily deployed to pull request January 26, 2026 13:18 Inactive
Signed-off-by: MarkAckert <35308966+MarkAckert@users.noreply.github.com>
Signed-off-by: MarkAckert <35308966+MarkAckert@users.noreply.github.com>
@github-actions github-actions bot temporarily deployed to pull request January 28, 2026 18:51 Inactive
Signed-off-by: MarkAckert <35308966+MarkAckert@users.noreply.github.com>
@github-actions github-actions bot temporarily deployed to pull request January 28, 2026 19:02 Inactive
Signed-off-by: MarkAckert <35308966+MarkAckert@users.noreply.github.com>
@github-actions github-actions bot temporarily deployed to pull request January 29, 2026 17:04 Inactive
Signed-off-by: MarkAckert <35308966+MarkAckert@users.noreply.github.com>
@github-actions github-actions bot temporarily deployed to pull request January 29, 2026 22:43 Inactive
Signed-off-by: MarkAckert <35308966+MarkAckert@users.noreply.github.com>
@github-actions github-actions bot temporarily deployed to pull request January 30, 2026 18:24 Inactive
Signed-off-by: MarkAckert <35308966+MarkAckert@users.noreply.github.com>
@github-actions github-actions bot temporarily deployed to pull request January 30, 2026 20:17 Inactive
Copy link
Collaborator

@anaxceron anaxceron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left some more comments re: minor edits. Let me know if you have questions.

Copy link
Collaborator

@anaxceron anaxceron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left some more comments re: minor edits. Let me know if you have questions.

MarkAckert and others added 2 commits February 2, 2026 10:51
Co-authored-by: anaxceron <ana.ceron@broadcom.com>
Signed-off-by: Mark Ackert <35308966+MarkAckert@users.noreply.github.com>
Co-authored-by: anaxceron <ana.ceron@broadcom.com>
Signed-off-by: Mark Ackert <35308966+MarkAckert@users.noreply.github.com>
@github-actions github-actions bot temporarily deployed to pull request February 2, 2026 16:01 Inactive
Signed-off-by: MarkAckert <35308966+MarkAckert@users.noreply.github.com>
Signed-off-by: MarkAckert <35308966+MarkAckert@users.noreply.github.com>
@github-actions github-actions bot temporarily deployed to pull request February 2, 2026 18:17 Inactive
MarkAckert and others added 5 commits February 2, 2026 13:22
…ice.md

Co-authored-by: anaxceron <ana.ceron@broadcom.com>
Signed-off-by: Mark Ackert <35308966+MarkAckert@users.noreply.github.com>
Co-authored-by: anaxceron <ana.ceron@broadcom.com>
Signed-off-by: Mark Ackert <35308966+MarkAckert@users.noreply.github.com>
Co-authored-by: anaxceron <ana.ceron@broadcom.com>
Signed-off-by: Mark Ackert <35308966+MarkAckert@users.noreply.github.com>
Co-authored-by: anaxceron <ana.ceron@broadcom.com>
Signed-off-by: Mark Ackert <35308966+MarkAckert@users.noreply.github.com>
Signed-off-by: MarkAckert <35308966+MarkAckert@users.noreply.github.com>
@MarkAckert MarkAckert requested a review from anaxceron February 2, 2026 18:28
@github-actions github-actions bot temporarily deployed to pull request February 2, 2026 18:41 Inactive
Signed-off-by: MarkAckert <35308966+MarkAckert@users.noreply.github.com>
Signed-off-by: MarkAckert <35308966+MarkAckert@users.noreply.github.com>
@github-actions github-actions bot temporarily deployed to pull request February 2, 2026 19:07 Inactive

* Scenario 1: Use a file-based (PKCS12) keystore with Zowe generated certificates
* Scenario 2: Use a file-based (PKCS12) keystore and import a certificate generated by another CA
* Scenario 3: Use a z/OS keyring-based keystore with Zowe generated certificates
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In previous files, keyring was updated to key ring. Here it is again keyring. Should we unify it?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you guys prefer? Maybe we should ask the TSC and add it to the Zowe style guide.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should use "key ring" outside code samples to align with IBM.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should use "key ring" outside code samples to align with IBM.

- 12.34.56.78
```
:::tip
To get the san IP address, run `ping dvipa.my-company.com` in your terminal.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In 9. is SAN used, here san.

-------------------------------------------------------------------------------
>> Generate Zowe certificate in keyring

>>>> Modify ZWEKRING
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The JCL sample would be ZWEIKRR1 for RACF, ZWEIKRT1 for TSS or ZWEIKRA1 for ACF2.

Corrected formatting of bullet points for clarity.

Signed-off-by: Martin Zeithaml <66114686+Martin-Zeithaml@users.noreply.github.com>
Signed-off-by: Martin Zeithaml <66114686+Martin-Zeithaml@users.noreply.github.com>
@github-actions github-actions bot temporarily deployed to pull request February 3, 2026 16:27 Inactive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: install and config Issues related to z/OS install and config release: V3 Zowe V3 content review: doc Needs review by Doc Squad member review: sme Needs review by an SME

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants