-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
UI unseal screen updates #11705
Conversation
There was a problem hiding this 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?
@@ -19,5 +20,9 @@ export default Controller.extend({ | |||
isUnsealed(data) { | |||
return data.sealed === false; | |||
}, | |||
|
|||
handleLicenseError() { | |||
this.set('showLicenseError', true); |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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
* 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
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: