| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
feat(cli): support mtls (#7325) ## Summary - Let the CLI present a client certificate when talking to a self-hosted Nango API behind mTLS, so customers no longer have to disable mTLS for `deploy` / `dryrun` / `pull`. - Configure it with `NANGO_CLI_TLS_CERT` (path to a PEM). A file that contains both cert and key is enough; `NANGO_CLI_TLS_KEY` / `NANGO_CLI_TLS_CA` cover split files and a private CA. - The same TLS agent is used on every CLI-to-API path (axios, fetch, and the Node SDK). Invalid cert/key pairs fail at load time. <!-- This is an auto-generated description by cubic. --> <a href="https://cubic.dev/pr/NangoHQ/nango/pull/7325?utm_source=github" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true"><picture><source media="(prefers-color-scheme: dark)" srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img alt="Review in cubic" src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a> <!-- End of auto-generated description by cubic. --> --------- Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> | 1 个月前 | |
fix(runner-sdk): stop retry on 401 for invalid credentials with provider retry.error_code (#5992) <!-- Describe the problem and your solution --> Runner SDK explicitly looks for `retry.reason === 'status_code_401'` to stop retries early on invalid credentials. A different retry reason is used if the code is matched against `proxyConfig.provider.proxy.retry.error_code` resulting in continuous retries against 401. Documentation around retries is also a bit misleading and needs clarification on when requests are retried. <!-- Issue ticket number and link (if applicable) --> [NAN-5415: Proxy continues retrying on 401](https://linear.app/nango/issue/NAN-5415/proxy-continues-retrying-on-401) <!-- Testing instructions (skip if just adding/editing providers) --> 1. Setup a test connection to a provider that specifies `401` in `retry.error_code` 2. Modify the credentials so they are no longer valid and won't refresh 3. Send a proxy request and see it stop after first retry | 4 个月前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 1 个月前 | ||
| 4 个月前 |