Update changelog for version 1.0.6 and add security configuration documentation

- Documented the use of NODE_TLS_REJECT_UNAUTHORIZED for TLS settings in changelog.
- Added detailed TLS configuration guidelines in the security configuration section.
- Updated getting started guide to include TLS configuration for self-signed certificates.
- Included security configuration in the sidebar for easier navigation.
- Bumped version to 1.0.6 in package.json and package-lock.json.

Author: minitriga

CHANGELOG.md

@@ -6,6 +6,12 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 
 <!-- towncrier release notes start -->
 
+## [1.0.6](https://github.com/opsmill/infrahub-vscode/tree/v1.0.6) - 2025-11-07
+
+### Changed
+
+- Use NODE_TLS_REJECT_UNAUTHORIZED environment variable instead of passing TLS options to SDK when tls_insecure is enabled. ([#46](https://github.com/opsmill/infrahub-vscode/issues/46))
+
 ## [1.0.5](https://github.com/opsmill/infrahub-vscode/tree/v1.0.5) - 2025-11-07
 
 ### Added

changelog/46.changed.md

@@ -69,6 +69,22 @@ interface ServerConfig {
 }
 ```
 
+#### TLS Configuration Details
+
+The `tls_insecure` property controls TLS certificate verification behavior:
+
+- **Default value**: `false` (secure, certificates are verified)
+- **When `true`**: Disables certificate verification for development environments
+- **Scope**: Affects all HTTPS connections when any server has this enabled
+- **Security impact**: Makes connections vulnerable to man-in-the-middle attacks
+
+**Use cases for `tls_insecure: true`**:
+- Development servers with self-signed certificates
+- Internal testing environments with custom CA certificates
+- Docker containers with self-signed certificates
+
+**Never use in production** as it compromises security.
+
 ### Example Configuration
 
 ```json
@@ -336,6 +352,19 @@ Planned support for VSCode's secret storage API.
 | Commands not appearing | Wrong context | Ensure correct tree view item is selected |
 | Validation not working | Missing YAML extension | Install Red Hat YAML extension |
 | Token not working | Incorrect format or permissions | Verify token format and permissions |
+| TLS certificate errors | Self-signed or invalid certificates | Add `"tls_insecure": true` for development servers |
+| CERT_HAS_EXPIRED | Expired SSL certificate | Renew certificate or use `tls_insecure` for dev |
+| SELF_SIGNED_CERT_IN_CHAIN | Self-signed certificate | Use `"tls_insecure": true` for development |
+
+### TLS Error Messages
+
+The extension provides specific error messages for common TLS issues:
+
+- **"TLS Certificate expired - check tls_insecure setting"**: The server's certificate has expired
+- **"Self-signed certificate - check tls_insecure setting"**: The server uses a self-signed certificate
+- **"TLS Verification failed - check tls_insecure setting"**: General certificate verification failure
+
+These messages appear in the server tree view when connection attempts fail due to certificate issues.
 
 ### Debug Output