docs: mention allow-insecure troubleshooting#2747
Closed
zaidazmi wants to merge 1 commit into
Closed
Conversation
Author
|
Closing and reopening to rerun the Adobe CLA check after signing. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
#2742
Related Issues
Fixes #2742
This updates the
aem upcertificate troubleshooting section to mentionaem up --allow-insecureas a temporary last-resort workaround while obtaining the proper CA certificate. The existingNODE_EXTRA_CA_CERTSapproaches remain the recommended fixes.Validation:
npm run lintgit diff --checkDuplicate check: searched for
allowInsecure troubleshooting,allow-insecure README,Zscaler certificate, and open PRs referencing the issue; no duplicate PR found.Thanks for contributing!