-
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
Troubleshooting tip Keeping ZSS secure with TLS #1883 #1946
base: master
Are you sure you want to change the base?
Conversation
✔️ Deploy Preview for zowe-docs-master ready! 🔨 Explore the source changes: 419673b 🔍 Inspect the deploy log: https://app.netlify.com/sites/zowe-docs-master/deploys/61d0be2d12fb530008eab05b 😎 Browse the preview: https://deploy-preview-1946--zowe-docs-master.netlify.app |
The default, when the environment variable ZOWE_ZSS_SERVER_TLS=true is set. This will use the Zowe keystore for TLS certificate management. | ||
|
||
AT-TLS, as described here: https://docs.zowe.org/stable/user-guide/mvd-configuration/#configuring-zss-for-https | ||
Note that AT-TLS and ZOWE_ZSS_SERVER_TLS=true are mutually exclusive, but perform the same task of making ZSS use HTTPS. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would rephrase this to say, "AT-TLS must be disabled if TLS is enabled, and vice versa" instead of "mutually exclusive" just for clarity.
Signed-off-by: AbhishekJamhoriya [email protected]
Your checklist for this pull request
🚨Please review the guidelines for contributing to this repository.
If the changes in this PR is part of the next future release, make this pull request against the docs-staging branch which will be published at the next release boundary. If the changes in this PR are part of the current release, use the default base branch, master. For more information about branches, see https://github.com/zowe/docs-site/tree/master#understanding-the-doc-branches.
If this PR relates to GitHub issues in
docs-site
or other repositories, please list in Description, prefixed with close, fix or resolve keywords.Description (including links to related git issues)
Please describe your pull request.
❤️Thank you!