Skip to content

fix(tool): honor SSL verify toggles for API services#193

Merged
duguwanglong merged 1 commit into
mainfrom
fix/api-service-ssl-toggle
Apr 27, 2026
Merged

fix(tool): honor SSL verify toggles for API services#193
duguwanglong merged 1 commit into
mainfrom
fix/api-service-ssl-toggle

Conversation

@xiami762

Copy link
Copy Markdown
Contributor

Summary

  • wire OneSEC and NGTIP API handlers to honor the configured SSL verification toggle for outgoing HTTP requests
  • add HTTPS verification control to Qingteng connections and isolate its tests from local machine config
  • add regression coverage for enabled and disabled SSL verification paths across the affected API services

Test plan

  • uv run pytest tests/tool/test_onesec_api_tool.py
  • uv run pytest tests/tool/test_ngtip_api_tool.py tests/tool/test_qingteng_api_tool.py

Made with Cursor

Wire the OneSEC, NGTIP, and Qingteng API handlers to respect the configured SSL verification toggle so private deployments can bypass certificate checks when needed. Add regression tests that cover both enabled and disabled verification paths and isolate Qingteng tests from local machine config.

Made-with: Cursor
@duguwanglong duguwanglong merged commit 35708b4 into main Apr 27, 2026
2 checks passed
duguwanglong added a commit that referenced this pull request Apr 29, 2026
- Add `_resolve_verify_ssl` helper that reads `verify_ssl` /
  `ssl_verify` / `custom_settings.verify_ssl` (matches the
  onesec/qingteng/ngtip pattern from PR #193). The bottom
  "SSL 验证" form toggle writes to `custom_settings.verify_ssl`,
  which the handler previously ignored — causing the toggle to
  have no effect at runtime.
- Drop the standalone `verify_ssl` credential_field from
  _provider.yaml so the WebUI no longer renders a duplicate
  text input next to the bottom SSL toggle.
- Refresh _provider.yaml notes to describe the new SSL toggle
  resolution precedence.
duguwanglong pushed a commit to DearEmma/flocks that referenced this pull request May 18, 2026
Wire the OneSEC, NGTIP, and Qingteng API handlers to respect the configured SSL verification toggle so private deployments can bypass certificate checks when needed. Add regression tests that cover both enabled and disabled verification paths and isolate Qingteng tests from local machine config.
duguwanglong added a commit to DearEmma/flocks that referenced this pull request May 18, 2026
- Add `_resolve_verify_ssl` helper that reads `verify_ssl` /
  `ssl_verify` / `custom_settings.verify_ssl` (matches the
  onesec/qingteng/ngtip pattern from PR AgentFlocks#193). The bottom
  "SSL 验证" form toggle writes to `custom_settings.verify_ssl`,
  which the handler previously ignored — causing the toggle to
  have no effect at runtime.
- Drop the standalone `verify_ssl` credential_field from
  _provider.yaml so the WebUI no longer renders a duplicate
  text input next to the bottom SSL toggle.
- Refresh _provider.yaml notes to describe the new SSL toggle
  resolution precedence.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants