You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea of this feature is to log all encryptables read or edit accesses, to make it more transparent what users are accessing or editing encrypted data. More you should see, who changed which attribute with which value.
Always run the E2E-tests if you change something in the frontend, run the backend-tests if you change something in the backend and test always manually
ToDo
Familiarize your-self with paper-trail gem
Check if editing for example description only does not re-encrypt given username, password. If so, make sure re-encrypt is only done if value has changed. we have to track if there were changes in username or password to show it
Do not show what changed exactly for attribute description, just display that the value was changed but no previous value. (description can be a pretty long text and would kill the layout/table)
The idea of this feature is to log all encryptables read or edit accesses, to make it more transparent what users are accessing or editing encrypted data. More you should see, who changed which attribute with which value.
This feature is based on: Access- and changelog conception and the previous feature #564
Always run the E2E-tests if you change something in the frontend, run the backend-tests if you change something in the backend and test always manually
ToDo
The text was updated successfully, but these errors were encountered: