-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update certificate-configuration-scenarios.md #4033
base: master
Are you sure you want to change the base?
Conversation
I did the following: 1. Corrected a typo [Changed quetions to questions.] 2. Aligned name, label, and calabel in the same level.
😺 Thank you for creating this PR! To publish your content to Zowe Docs, follow these required steps.
Need help? Contact the Doc Squad in the #zowe-doc Slack channel. |
1 similar comment
😺 Thank you for creating this PR! To publish your content to Zowe Docs, follow these required steps.
Need help? Contact the Doc Squad in the #zowe-doc Slack channel. |
📁 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. |
1 similar comment
📁 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. |
Added/edited the following lines: #Type of certificate storage. Valid values are: PKCS12 or JCERACFKS createZosmfTrust: true #**COMMONLY_CUSTOMIZED** #Keystore directory caLabel: localca
- nwplzweb.dev.rocketsoftware.com - 10.17.224.13
Changed some of the indentations of terms inside the code block beginning with "dname"
I did the following:
Describe your pull request here:
List the file(s) included in this PR:
After creating the PR, follow the instructions in the comments.