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

Backport of VAULT-21435 Use seal wrappers rather than config to determine autoSeal barrier type. into release/1.15.x #24166

Conversation

hc-github-team-secure-vault-core
Copy link
Collaborator

@hc-github-team-secure-vault-core hc-github-team-secure-vault-core commented Nov 16, 2023

Backport

This PR is auto-generated from #24165 to be assessed for backporting due to the inclusion of the label backport/1.15.x.

The below text is copied from the body of the original PR.


A seal's Access object contains all seal configuration, which in the case of seal migration includes the "unwrap seal" as well as the barrier seal. Thus, to determine whether an autoSeal is of a specific type such as 'Transit' or whether it is a 'Multiseal', use the wrappers of the seal's Access.

In addition: Fix an error that resulted in the wrong seal type being reported while Vault is in seal migration mode.


Overview of commits

@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/victorr/vault-22031-fix-autoseal-barrier-type/currently-noted-buffalo branch from 387f785 to afa2bb3 Compare November 16, 2023 19:17
@hashicorp-cla
Copy link

hashicorp-cla commented Nov 16, 2023

CLA assistant check
All committers have signed the CLA.

@github-actions github-actions bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Nov 16, 2023
Copy link

CI Results:
All Go tests succeeded! ✅

…pe. (#24165)

* Use seal wrappers rather than config to determine autoSeal barrier type.

A seal's Access object contains all seal configuration, which in the case of
seal migration includes the "unwrap seal" as well as the barrier seal. Thus, to
determine whether an autoSeal is of a specific type such as 'Transit' or whether
it is a 'Multiseal', use the wrappers of the seal's Access.

* Fix seal type reported by /sys/seal-status.

Fix an error that resulted in the wrong seal type being reported while Vault is
in seal migration mode.
@victorr victorr force-pushed the backport/victorr/vault-22031-fix-autoseal-barrier-type/currently-noted-buffalo branch from a1a3c7b to 4c726a7 Compare November 16, 2023 20:14
@victorr
Copy link
Contributor

victorr commented Nov 16, 2023

Cherry-pick succeeded without errors once a previous fix was back ported: #24170.

@victorr victorr self-assigned this Nov 16, 2023
@victorr victorr added this to the 1.15.3 milestone Nov 16, 2023
@victorr victorr marked this pull request as ready for review November 16, 2023 20:16
@victorr victorr requested a review from a team as a code owner November 16, 2023 20:16
@victorr victorr enabled auto-merge (squash) November 16, 2023 20:16
Copy link

Build Results:
All builds succeeded! ✅

@victorr victorr merged commit 825e242 into release/1.15.x Nov 16, 2023
@victorr victorr deleted the backport/victorr/vault-22031-fix-autoseal-barrier-type/currently-noted-buffalo branch November 16, 2023 20:30
@victorr victorr changed the title Backport of Use seal wrappers rather than config to determine autoSeal barrier type. into release/1.15.x Backport of VAULT-21435 Use seal wrappers rather than config to determine autoSeal barrier type. into release/1.15.x Nov 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants