Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

options.customFetch is not included in jwks.fetchJwks call #760

Closed
2 tasks done
tripodsan opened this issue Feb 25, 2025 · 2 comments
Closed
2 tasks done

options.customFetch is not included in jwks.fetchJwks call #760

tripodsan opened this issue Feb 25, 2025 · 2 comments
Labels
bug Something isn't working

Comments

@tripodsan
Copy link

What happened?

since 6.0, the remote jwks always uses the global fetch. the suggested options.customFetch doesn't work, as it is not passed to the fetchJwks method:

signal: AbortSignal.timeout(this._timeoutDuration),

Version

6.0.0

Runtime

Node.js

Runtime Details

$ node --version v22.12.0

Code to reproduce

.

Required

  • I have searched the issues tracker and discussions for similar topics and couldn't find anything related.
  • I agree to follow this project's Code of Conduct
@panva
Copy link
Owner

panva commented Feb 25, 2025

Thanks, i'll take a look

@panva panva added bug Something isn't working and removed triage labels Feb 25, 2025
panva added a commit that referenced this issue Feb 25, 2025

Verified

This commit was signed with the committer’s verified signature.
closes #760
@panva
Copy link
Owner

panva commented Feb 25, 2025

Fixed in https://github.com/panva/jose/releases/tag/v6.0.7

@panva panva closed this as completed Feb 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants