[storage][blob-batch] Getting TlsVersionNotPermitted with batch operations

[ljian3377]

The test cases for batch operations fail on some storage accounts but succeeded on others.

azure-sdk-for-js/sdk/storage/storage-blob/test/blobbatch.spec.ts

Line 105 in 8c2cf0b

it("deleteBlobs should work for batch delete", async () => {

Found in regression. And accroding to Ashish's comment in this .NET issue: Azure/azure-sdk-for-net#13524 (comment)
this is a bug on the service.

[ljian3377]

@jiacfan did some digging and found that the service may be working as designed.
The account has the "Mininum TLS version" set as "Version 1.2", which is the default in the portal when creating an account.

But how can a customer send TLS "Version 1.2" request with our SDK? I did some digging but failed to find a way.
@jeremymeng do we have support for specifying the TLS version?

[ramya-rao-a]

But how can a customer send TLS "Version 1.2" request with our SDK

I doubt if a customer can do this.
@sarangan12 I recall you had done some investigation in this area. Can you share any details?

@ljian3377,
Can you share more details on how you encountered the failure?
Do you see this in CI or when you run manually?
Do you see it when using certain node versions?

[ljian3377]

Can you share more details on how you encountered the failure?
Do you see this in CI or when you run manually?
Do you see it when using certain node versions?

I encountered this when testing manually at local. I created an account with "Mininum TLS version" set as "Version 1.2". I am using Node.js v12.18.4.
According to this comment, TLSv1.2 is the default TLS minimum? Then I don't know why it failed. How to find out which version we are acctually using.

nodejs/node#27666 (comment)

  --tls-max-v1.2                            set default TLS maximum to TLSv1.2 (default: TLSv1.3)
  --tls-max-v1.3                            set default TLS maximum to TLSv1.3 (default: TLSv1.3)
  --tls-min-v1.0                            set default TLS minimum to TLSv1.0 (default: TLSv1.2)
  --tls-min-v1.1                            set default TLS minimum to TLSv1.1 (default: TLSv1.2)
  --tls-min-v1.3                            set default TLS minimum to TLSv1.3 (default: TLSv1.2)

[amishra-dev]

this should have been fixed by now. @ljian3377 can you confirm

[ljian3377]

this should have been fixed by now. @ljian3377 can you confirm

Yes. The batch operations now work with an account whose "Mininum TLS version" is set as "Version 1.2".

@ramya-rao-a
I am fine with closing this issue if the support/documentation for specifying the TLS version can't be added.