Skip to content

feat: pass SSL/connect options through to Req in HTTP client#9

Merged
scrogson merged 2 commits intoscrogson:masterfrom
spunkedy:ssl-options-passthrough
Feb 5, 2026
Merged

feat: pass SSL/connect options through to Req in HTTP client#9
scrogson merged 2 commits intoscrogson:masterfrom
spunkedy:ssl-options-passthrough

Conversation

@spunkedy
Copy link
Copy Markdown
Contributor

@spunkedy spunkedy commented Feb 5, 2026

Summary

  • Forward connect_options from http_opts to Req, enabling SSL/TLS configuration
  • Add documentation with SSL configuration examples
  • Add integration test for connect_options pass-through

Problem

The HTTP client ignored SSL options when fetching JWKS, causing failures with self-signed certificates in dev/staging environments.

Usage

NoWayJose.start_jwks_fetcher("auth0", url,
  http_opts: [
    connect_options: [
      transport_opts: [verify: :verify_none]
    ]
  ]
)

Test plan

  • Existing tests pass
  • New integration test verifies connect_options are forwarded

The default HTTP client now forwards `connect_options` to Req,
enabling SSL/TLS configuration for JWKS fetching. This allows
disabling certificate verification for self-signed certificates
in development/staging environments.

Usage:
  NoWayJose.start_jwks_fetcher("auth0", url,
    http_opts: [
      connect_options: [
        transport_opts: [verify: :verify_none]
      ]
    ]
  )
@spunkedy spunkedy marked this pull request as draft February 5, 2026 09:14
@spunkedy spunkedy marked this pull request as ready for review February 5, 2026 20:23
@scrogson scrogson merged commit 55ed0d2 into scrogson:master Feb 5, 2026
11 checks passed
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