Skip to content

Conversation

@ArooshLele
Copy link
Collaborator

@ArooshLele ArooshLele commented Sep 3, 2025

Describe your pull request here:
The diagrams depict some rules of AT-TLS.
I will eventually place these diagrams into the file:
user-guide/configuring-at-tls-for-zowe-server.md

List the file(s) included in this PR:

After creating the PR, follow the instructions in the comments.
CC: @ArooshLele @gauravs-20

These diagrams depict some rules of AT-TLS.

Signed-off-by: ArooshLele <[email protected]>
@ArooshLele ArooshLele self-assigned this Sep 3, 2025
@ArooshLele ArooshLele added priority-medium area: install and config Issues related to z/OS install and config release: V3 Zowe V3 content review: sme Needs review by an SME labels Sep 3, 2025
@github-actions
Copy link

github-actions bot commented Sep 3, 2025

😺 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.

1 similar comment
@github-actions
Copy link

github-actions bot commented Sep 3, 2025

😺 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

github-actions bot commented Sep 3, 2025

@github-actions github-actions bot temporarily deployed to pull request September 3, 2025 13:38 Inactive
Copy link
Collaborator

@Martin-Zeithaml Martin-Zeithaml Sep 5, 2025

Choose a reason for hiding this comment

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

We are usually using defaults, for Zowe Server the user is ZWESVUSR. Is there a reason for using different user name ZWEUSR?

Right box: capital letter for the first word.

For all pictures:

  • zOSMF -> z/OSMF
  • Turn off the spell check when taking the screenshot

Copy link
Member

Choose a reason for hiding this comment

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

There is no ZWEUSR in the documentation as of this time, so as you say ZWESVUSR is the clear winner.

Copy link
Collaborator Author

@ArooshLele ArooshLele Oct 27, 2025

Choose a reason for hiding this comment

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

@Martin-Zeithaml @1000TurquoisePogs Thanks for the feedback. The user name is changed to ZWESVUSR in the diagrams.
CC: @gauravs-20 @ArooshLele

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 priority-medium release: V3 Zowe V3 content review: sme Needs review by an SME

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants