fredwes

We've worked on it for a few months but only recently got approval to submit a PR. Would love to get your feedback! 😄

@IanChokS The only key store supported by this PR is Azure Key Vault. Additional key stores can be added by implementing a `decryptColumnEncryptionKey` method

Thanks @arthurschreiber! I fixed the issues you raised so far and fixed the rest of the failing tests. I'm going to continue to add additional test cases as you complete...

@arthurschreiber That's a good idea, I think there are some other things that can be split out into separate PRs as well (and cleaned up). I can do it or...

@arthurschreiber Always Encrypted does support PLP, but for the purpose of `toBuffer` we don't use PLP terminators, the _entire_ parameter value is used during encryption/decryption

@arthurschreiber There is no implementation necessary from an Always Encrypted perspective. It should be supported implicitly using existing parameter writing and reading logic. You are right, PLP streaming for Always...

@Sathishabm210 are you using tedious master branch or this PR branch? Always Encrypted feature isn’t merged yet to master. If you are using this PR branch then I see that...

@Sathishabm210 @jocund Looks like there is a bug with my code. `RSA-HSM` should be allowed. This PR has gotten out of date with the master branch. I will make sure...

> @fredwes Commented this line in your lib folder file 'keystore-provider-azure-key-vault' that checks 'RSA' to allow 'RSA-HSM' based keys. It worked to help execute successful pull queries > > //...

@jocund I think the issue is that you will need to specify the collation in the parameter options. ```javascript request.addParameter('name', TYPES.Char, 'value', { collation: { sortId: 52, lcid: 0, flags:...