[PSWDMNGR-10] Password manager should not depend on the activation keypair Created: 14/Mar/18  Updated: 01/Feb/24

Status: Reopened
Project: Password Manager
Component/s: None
Affects Version/s: 1.2
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Ondrej Chytil Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Team: AdminX

 Description   

Right now the Password manager uses the activation keypair to encrypt/decrypt stored passwords. This becomes a problem when the key needs to be re-generated or when the keypair is not kept when moving an instance to another environment. Passwords are essentially lost at this case.

Generation of the activation keypair is possible via the UI so it's relatively easy to get to this issue.

Possible solutions:

  • make independent keys for password manager
  • re-encode all passwords when the new activation key is generated
  • at least let the user know via an alert what are the implications of generating new key

 


Generated at Mon Feb 12 10:25:59 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.