Skip to content

OnEncrypt and OnDecrypt in KMS Keyring contains wrong key id for the keyring trace #60

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
WesleyRosenblum opened this issue Dec 10, 2019 · 1 comment

Comments

@WesleyRosenblum
Copy link
Contributor

The OnEncrypt and OnDecrypt specs for the KMS Keyring say that in the resulting Keyring trace:

"The string field KeyName contains generator."

The KeyName should either be the keyId the user specified (which may be an alias) or the ARN returned by KMS.

@WesleyRosenblum
Copy link
Contributor Author

This was fixed in #50

@mattsb42-aws mattsb42-aws added this to the keyrings milestone May 15, 2020
josecorella pushed a commit that referenced this issue Jun 7, 2023
Moving some of the interface
from the local CMC to the CMC Interface.

Using the CMC requires a consistent interface.
Currently the Caching CMM has an interface
that relies on the Local CMC.
This means that if a CMC was created according
to the specification it would not function correctly.
josecorella pushed a commit that referenced this issue Jun 7, 2023
Moving some of the interface
from the local CMC to the CMC Interface.

Using the CMC requires a consistent interface.
Currently the Caching CMM has an interface
that relies on the Local CMC.
This means that if a CMC was created according
to the specification it would not function correctly.
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

2 participants