Merging to release-5.7: [TT-13914] Fix typo in config flag name (#5914)

[buger]

User description

TT-13914 Fix typo in config flag name (#5914)

---

PR Type

Documentation

---

Description

• Corrected a typo in the TLS configuration flag name.

• Replaced ssl_secure_skip_verify with ssl_insecure_skip_verify.

• Updated TLS configuration examples for consistency.

• Ensured accurate descriptions for the corrected flag.

---

Changes walkthrough 📝

Relevant files

Documentation

tyk-open-source.md Corrected TLS flag typo in open-source documentation          tyk-docs/content/tyk-open-source.md Replaced ssl_secure_skip_verify with ssl_insecure_skip_verify. Updated TLS configuration examples for consistency. Adjusted descriptions to reflect the corrected flag name. +8/-8      tyk-self-managed.md Corrected TLS flag typo in self-managed documentation        tyk-docs/content/tyk-self-managed.md Replaced ssl_secure_skip_verify with ssl_insecure_skip_verify. Updated TLS configuration examples for consistency. Adjusted descriptions to reflect the corrected flag name. +4/-4

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

🎫 Ticket compliance analysis ✅ 5914 - Fully compliant Fully compliant requirements: Correct a typo in the configuration flag name. Replace all instances of ssl_secure_skip_verify with ssl_insecure_skip_verify. Ensure consistency in documentation for TLS configuration examples. Not compliant requirements:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Possible Misleading Wording The description for ssl_insecure_skip_verify should emphasize the risks of using this flag in non-production environments more explicitly to avoid potential misuse. - `storage.ssl_insecure_skip_verify`: A flag that, when set to true, instructs the application not to verify the Redis server's TLS certificate. This is not recommended for production due to the risk of `man-in-the-middle` attacks.

[github-actions]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Security	Clarify security risks of insecure flag Clarify in the documentation that setting ssl_insecure_skip_verify to true should only be used for testing or development purposes and explicitly state the potential security risks in more detail to ensure users understand the implications. tyk-docs/content/tyk-open-source.md [959] -- `storage.ssl_insecure_skip_verify`: A flag that, when set to true, instructs the application not to verify the Redis server's TLS certificate. This is not recommended for production due to the risk of `man-in-the-middle` attacks. +- `storage.ssl_insecure_skip_verify`: A flag that, when set to true, instructs the application not to verify the Redis server's TLS certificate. This should only be used for testing or development purposes as it exposes the connection to potential `man-in-the-middle` attacks, compromising data security. Suggestion importance[1-10]: 8 Why: The suggestion improves the documentation by explicitly clarifying that the ssl_insecure_skip_verify flag should only be used for testing or development purposes and elaborates on the security risks. This enhances user understanding and promotes secure practices.	8
	Highlight production risks of insecure flag Emphasize that ssl_insecure_skip_verify should never be used in production environments and provide a recommendation to always validate certificates in production for secure communication. tyk-docs/content/tyk-self-managed.md [4354] -- `storage.ssl_insecure_skip_verify`: A flag that, when set to true, instructs the application not to verify the Redis server's TLS certificate. This is not recommended for production due to the risk of `man-in-the-middle` attacks. +- `storage.ssl_insecure_skip_verify`: A flag that, when set to true, instructs the application not to verify the Redis server's TLS certificate. This should never be used in production environments as it exposes the connection to `man-in-the-middle` attacks. Always validate certificates in production for secure communication. Suggestion importance[1-10]: 8 Why: The suggestion emphasizes the critical importance of not using ssl_insecure_skip_verify in production and recommends validating certificates for secure communication. This addition strengthens the documentation by promoting best practices and mitigating security risks.	8

[netlify]

✅ PS. Pls add /docs/nightly to the end of url

Name	Link
🔨 Latest commit	f842bfe
🔍 Latest deploy log	https://app.netlify.com/sites/tyk-docs/deploys/6791e46849f1d6000777ca93
😎 Deploy Preview	https://deploy-preview-5917--tyk-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.