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

feat: Insomnia vault key management UI[INS-4715] #8296

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

cwangsmv
Copy link
Contributor

Changes:
As part of the Insomnia vault feature, this PR includes the UI changes for vault key management.
The vault key is used to encrypt local secret environment variables.

Add a new UI in Preferences page for vault key generation:
Screenshot 2025-01-15 at 10 18 10

When user has logged on other devices/re-login, user needs to enter the vault key for validation. We also provide reset feature if the vault key is lost.
Screenshot 2025-01-15 at 10 18 17

There will be two new options related to vault key:
User could choose to save the encrypted vault key locally to avoid entering vault key after re-login. The vault key is encrypted using OS native secret manager(like KeyChain in MacOS).
There's another option to choose whether to allow pre-request/post-response scripts to access secret environment variables
Screenshot 2025-01-15 at 10 18 54

@cwangsmv cwangsmv requested review from jackkav and ihexxa January 15, 2025 02:35
ihexxa
ihexxa previously approved these changes Jan 15, 2025
Copy link
Contributor

@ihexxa ihexxa left a comment

Choose a reason for hiding this comment

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

Overall lgtm from my side as I've reviewed this part several rounds in #8233

packages/insomnia/src/main/window-utils.ts Outdated Show resolved Hide resolved
@cwangsmv cwangsmv force-pushed the feat/insomnai-vault-setting-ui branch from 0730ce9 to d0f5b17 Compare January 15, 2025 09:06
return;
}

const to = fs.createWriteStream(outputPath);
Copy link
Member

@CurryYangxx CurryYangxx Jan 17, 2025

Choose a reason for hiding this comment

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

I suggest we don't use nodeJs module directly in render process for security and maintainability reasons.

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

Successfully merging this pull request may close these issues.

3 participants