Skip to content

Encryption Context for DecryptionMaterials on v3.0.0 #2036

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
alexyap1205 opened this issue Jun 5, 2024 · 4 comments
Closed

Encryption Context for DecryptionMaterials on v3.0.0 #2036

alexyap1205 opened this issue Jun 5, 2024 · 4 comments

Comments

@alexyap1205
Copy link

Migrating from v2.4.1 to v3.0.0, we noticed that the DecryptionMaterials has an additional property encryptionContext. For 2.4.1, we didn't have this and we don't plan to use encryption context from Encryption SDK. However, upgrading to 3.0.0 requires us to provide an encryption context, otherwise DecryptionHandler fails with null exception. Should we just provide an emptyMap? Is it the same as saying there's no encryption context?

This is the piece of code from that throws null exception at runtime. TIA.

@lucasmcdonald3
Copy link
Contributor

Hi @alexyap1205,

Thanks for the report!
We are investigating this issue and may have identified an issue with custom CMMs from earlier versions of the ESDK.

Are you using a custom CMM?
If so, can you provide enough details about it so that we can produce this error?

Thanks,
Lucas

@lucasmcdonald3
Copy link
Contributor

Hi @alexyap1205,

We recently released a patch to the ESDK (3.0.1) that fixes an issue with custom CMMs from earlier versions of the ESDK.

Could you consume this new version and let us know if it fixes your issue?

Thanks,
Lucas

@alexyap1205
Copy link
Author

Hi @lucasmcdonald3, sorry I was busy with other things. Thanks for the fix. Will give it a go.

@ShubhamChaturvedi7
Copy link

ShubhamChaturvedi7 commented Jul 5, 2024

@alexyap1205 Closing this issue since we have released the patch and haven't heard from you for some time. Feel free to open a new issue if the problem is still present in the patch.

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

No branches or pull requests

3 participants