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

UI unseal screen updates #11705

Merged
merged 6 commits into from
May 26, 2021
Merged

UI unseal screen updates #11705

merged 6 commits into from
May 26, 2021

Conversation

hashishaw
Copy link
Collaborator

This change updates the style and language on the Vault unseal screen, and adds a specific view when a login attempt fails with the error licensing is in an invalid state. There are now links to relevant documentation on both the unseal form and the license error view.

As you can see from the gif below, it still shows other errors correctly on the unseal form itself, and then disallows the ability to try to unseal once a licensing error is detected:

unseal-license-terminated

@hashishaw hashishaw added this to the 1.8 milestone May 26, 2021
Copy link
Contributor

@Monkeychip Monkeychip left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great. Only additional comments are a changelog and you currently have the label at 1.8 but shouldn't it be 1.7 if we're backporting it to 1.7?

ui/lib/core/addon/components/shamir-flow.js Outdated Show resolved Hide resolved
@@ -19,5 +20,9 @@ export default Controller.extend({
isUnsealed(data) {
return data.sealed === false;
},

handleLicenseError() {
this.set('showLicenseError', true);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we still use this.set?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, possibly because this is in a controller? I considered moving all of this logic to a separate component that we can glimmerize but that seemed out of scope for this, especially considering the backport

@hashishaw hashishaw modified the milestones: 1.8, 1.7.3 May 26, 2021
@vercel vercel bot temporarily deployed to Preview – vault-storybook May 26, 2021 18:41 Inactive
@vercel vercel bot temporarily deployed to Preview – vault May 26, 2021 18:41 Inactive
@hashishaw hashishaw merged commit 151bfa9 into master May 26, 2021
@hashishaw hashishaw deleted the ui/unseal-screen branch May 26, 2021 18:59
hashishaw added a commit that referenced this pull request May 26, 2021
* Styling for empty-state and splash-page

* Update shamir-flow language and trigger onError on non-400 error

* Add license terminated screen to unseal

* Add changelog
hashishaw added a commit that referenced this pull request May 26, 2021
* Styling for empty-state and splash-page

* Update shamir-flow language and trigger onError on non-400 error

* Add license terminated screen to unseal

* Add changelog
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants