Skip to content
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

Bump aws-dynamodb-encryption-java from 1.13.0 to 1.15.0 #35

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Feb 8, 2021

Bumps aws-dynamodb-encryption-java from 1.13.0 to 1.15.0.

Release notes

Sourced from aws-dynamodb-encryption-java's releases.

DynamoDB Encryption Client Java - Release 1.15.0

Adds the CachingMostRecentProvider and deprecates MostRecentProvider.

Time-based key reauthorization logic in MostRecentProvider did not re-authorize the use of the key after key usage permissions were changed at the key provider (for example AWS Key Management Service). This created the potential for keys to be used in the DynamoDB Encryption Client after permissions to do so were revoked.

CachingMostRecentProvider replaces MostRecentProvider and provides a cache entry TTL to reauthorize the key with the key provider.

MostRecentProvider is now deprecated, and is removed in 2.0.0. See https://docs.aws.amazon.com/dynamodb-encryption-client/latest/devguide/most-recent-provider.html#mrp-versions for more details.

1.15.0 also fixes interoperability issues between the Python and Java implementations of DynamoDB Encryption Client.

Changelog

Sourced from aws-dynamodb-encryption-java's changelog.

1.15.0 -- 2021-02-04

Adds the CachingMostRecentProvider and deprecates MostRecentProvider.

Time-based key reauthorization logic in MostRecentProvider did not re-authorize the use of the key after key usage permissions were changed at the key provider (for example AWS Key Management Service). This created the potential for keys to be used in the DynamoDB Encryption Client after permissions to do so were revoked.

CachingMostRecentProvider replaces MostRecentProvider and provides a cache entry TTL to reauthorize the key with the key provider.

MostRecentProvider is now deprecated, and is removed in 2.0.0. See https://docs.aws.amazon.com/dynamodb-encryption-client/latest/devguide/most-recent-provider.html#mrp-versions for more details.

1.15.0 also fixes interoperability issues between the Python and Java implementations of DynamoDB Encryption Client.

1.14.1 -- 2019-10-14

Fixes com.amazonaws:aws-dynamodb-encryption-java so that it may be consumed in mavenCentral.

1.14.0 -- 2019-10-14

Use 1.14.1 instead. This release relies on a dependency that isn't available in mavenCentral.

Minor Changes

  • Add ExtraDataSupplier to Metastore #76
  • Add support for overriding KMS requests in DirectKMSMaterialProvider #76
  • Allow DoNotEncrypt and DoNotTouch to be used at a field level #95
  • Allow overriding KMS encryption context #102

Maintenance

  • Migrate from JUnit to TestNG
  • Added JaCoCo for code coverage
  • Replace Base64 implementation with Java 8's #82
  • Added checkstyle
  • Upgrade Bouncy Castle from 1.61 to 1.65 #119
Commits
  • 7de5f5a feat: Adds the CachingMostRecentProvider. Deprecates MostRecentProvider.
  • 14c6a95 chore: Remove codecov from CI (#128)
  • a1eac91 chore: Remove Travis CI (#126)
  • 0c6a1dc chore: Add AWS CodeBuild buildspec (#125)
  • fed2f10 fix: Remove sdk2 from release branch, maintained in sdk2-snapshot branch (#124)
  • e2ec652 chore: Add CONTRIBUTING.md and security reports.
  • 6d56f25 Update CONTRIBUTING.md
  • 752a10c chore: Add CONTRIBUTING.md and security reports.
  • 41ad9bf Upgrade Bouncy Castle from 1.61 to 1.65 (#119)
  • 53b80a1 Update checkstyle dependencies
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Feb 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants