-
Notifications
You must be signed in to change notification settings - Fork 122
Backwards compatibility issue with alias/name and getMasterkey #50
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
Labels
Comments
So creating the full ARN from the alias seems to be the new way of doing this.
|
This is a regression. Reopening to fix. |
bdonlan
pushed a commit
to bdonlan/aws-encryption-sdk-java
that referenced
this issue
Apr 5, 2018
The default region was not actually being consulted when presented with a regionless key ID (such as a bare UUID or an "alias/foo" value). Fixes aws#50.
Note that when using the builder it is intentional that you need to specify a default region, but that also is currently broken. When using legacy constructors we intended for behavior to be unchanged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In
1.3.1
I could get aMasterKeyProvider
using aliases and regions. In the code below I have a list of regions (this.regions
) where the alias (this.keyId
) has been created in each. I create theKmsMasterKeyProvider
for each region and return aMultiProvider
.I can then use the
MultiProvider
withAwsCrypto
like so...This no longer works. The
getMasteKeyMethod
at line 452 of theKmsMasterKeyProvider.java
now requires an ARN for the keyId.The result is that
regionName
isnull
.Is there another way to do what I'm trying to do? Thanks.
M
The text was updated successfully, but these errors were encountered: