Skip to content

Restore User-Agent for superagent@10 login compatibility (v1.1.8) - #29

Open
baraka-akeyless wants to merge 3 commits into
mainfrom
fix/restore-user-agent-superagent10
Open

Restore User-Agent for superagent@10 login compatibility (v1.1.8)#29
baraka-akeyless wants to merge 3 commits into
mainfrom
fix/restore-user-agent-superagent10

Conversation

@baraka-akeyless

Copy link
Copy Markdown
Member

Summary

  • Confirmed customer report: superagent@10.3.0 (forced in v1.1.7 to fix url.parse DEP0169) sends no User-Agent, while superagent@3.7.0 always sent node-superagent/3.7.0.
  • Some Gateways / ingress / WAF policies reject requests without a User-Agent → Failed to login to Akeyless on configs that worked on v1.1.6.
  • Fix: set User-Agent: node-superagent/3.7.0 akeyless-github-action on ApiClient defaultHeaders (keeps superagent@10 / no DEP0169).
  • Bump version to v1.1.8.

Test plan

  • npm test (34 tests, including new HTTP capture asserting User-Agent is sent)
  • npm run package
  • Local auth request against mock server shows restored UA; no DEP0169 on auth path
  • Customer retest against their Gateway with @fix/restore-user-agent-superagent10 or @v1.1.8 after release

Made with Cursor

baraka-akeyless and others added 3 commits July 22, 2026 20:55
v1.1.7 forced superagent@10 for the url.parse fix, but that client no longer sends a default User-Agent. Some Gateway/WAF setups reject those requests as Failed to login to Akeyless; restore the v1.1.6-compatible UA on ApiClient default headers.

Co-authored-by: Cursor <cursoragent@cursor.com>
AWS IAM cloud-id failures and API auth errors are now included in setFailed so self-hosted test runs show the root cause without enabling debug.

Co-authored-by: Cursor <cursoragent@cursor.com>
Smithy SignatureV4 caused SignatureDoesNotMatch when Akeyless replayed GetCallerIdentity; match akeyless-cloud-id's aws4 header layout while keeping AWS SDK v3 credentials and superagent@10.

Co-authored-by: Cursor <cursoragent@cursor.com>
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.

1 participant