fix(middleware-websocket): pass options to presign in WebsocketSignatureV4 sign

[trivikr]

Issue

Fixes: #5011

Description

When systemClockOffset is set for RekognitionStreamingClient, the updated signingDate is not passed in presigned URL, and the presigner uses default Date.now(). This results in InvalidSignatureException on a websocket connection.

This PR passes the signing options while presigning the URL which includes updated signing date.

Testing

Used repro from #5011

No system clock offset

System time is 8:28am Pacific, and X-Amz-Date is 152800 UTC. No errors are returned

System Clock Offset of one hour

In this setup, the system time is manually set ahead by one hour, and a systemClockOffset of negative one hour (-3600000) passed in RekognitionStreamingClient.

The System time is 9:29am Pacific, but X-Amz-Date is 152918 UTC as required. No errors are returned.

Enabled client-transcribe-streaming E2E test which uses websocket, and verified that it's succeessful.

$ client-transcribe-streaming> yarn test:e2e
yarn run v1.22.17
$ jest --config jest.config.e2e.js
 PASS  test/index.e2e.spec.ts (8.079 s)
  TranscribeStream client
    ✓ should stream the transcript (5091 ms)

Test Suites: 1 passed, 1 total
Tests:       1 passed, 1 total
Snapshots:   0 total
Time:        8.126 s
Ran all test suites.
Done in 8.88s.

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.