yuki / myVault

A web interface for HashiCorp Vault which allow to edit secrets with a Markdown editor
https://yuki.github.io/myVault/
GNU General Public License v3.0
0 stars 0 forks source link

Append actions to secrets #53

Open yuki opened 6 years ago

yuki commented 6 years ago

Right now, when a secret is locked, we append a json parameter "username" to the secret, to know who has locked it. The idea is to know who and what was the last action has done.

There should be new parameters, with the secret itself:

In the future, when the admin area has done, there will be an option to delete historic backups.

With this, we have an historic of the secret, something like:

Current: 2017-12-01 8:44 {action: closed, by: username2, secret: ...., locked_by: null}
Backup: 2017-12-01 8:43 {action: updated, by: username2, secret: ...., locked_by: username2}
Backup: 2017-12-01 8:40 {action: locked, by: username2, secret: ...., locked_by: username2}
Backup: 2017-12-01 8:40 {action: unlocked, by: username2, secret: ...., locked_by: null}
Backup: 2017-12-01 8:35 {action: auto-saved, by: username1, secret: ...., locked_by: username1}
Backup: 2017-12-01 8:32 {action: updated, by: username1, secret: ...., locked_by: username1 }
Backup: 2017-12-01 8:30 {action: created, by: username1, secret: ...., locked_by: username1}
yuki commented 6 years ago

All the new secrets will have those options with the previous commit. I must create the "log" section in the admin area to visualize this.

The idea is to have the actual secret tree, select one, and visualize all this info. For this, I must read all the secret's backup to read the options.