View Issue Details

Jump to NotesJump to History
This issue affects 1 person(s).
 4
IDProjectCategoryView StatusDate SubmittedLast Update
14926Feature requestsSurvey participants (Tokens)public2019-05-22 10:032019-05-22 19:59
ReporterDenisChenu Assigned Todominikvitt 
PriorityhighSeverityfeature 
Status closedResolutionno change required 
Product Version4.0.0dev 
Summary14926: Don't set encrypted firstname + lastname column by default
Description

In 413 DB update firstname and lastname of old surveys are set to encrypted by default.

  1. I think it's better if encrypted are an Opt In system (with a GUI global settings for default behaviour for new survey)
  2. I think feature must not be forced on old survey, because there are user with SQL direct read and update system.
Additional Information

And here : it take a long time to update all token table, update are already very long …

TagsNo tags attached.
Bug heat4
Story point estimate
Users affected %

Relationships

Relationship GraphDependency Graph
related to 14874 closedDenisChenu Bug reports This DB send a 504 when upgrade … 

Users monitoring this issue

There are no users monitoring this issue.

Activities

dominikvitt

dominikvitt

2019-05-22 10:54

developer   ~52029

In the context of GDPR, and since those fields are considered personal information, this data should be protected while on the database.
That is way firstname, lastname and email fields are set to be automatically encrypted.
DenisChenu

DenisChenu

2019-05-22 12:06

developer   ~52033

Last edited: 2019-05-22 12:07
  1. This broke upgrade in a lot of configuration …
  2. Updating something previously not encrypted it's a bad behaviour

Why not : set default to encrypted but set old survey to not encrypted …

And all our user are not GPDR related …
dominikvitt

dominikvitt

2019-05-22 12:44

developer   ~52040

Upgrade 413 encrypts only token and participant tables, not surveys and responses.
DenisChenu

DenisChenu

2019-05-22 12:49

developer   ~52042

Yes, and if you have a lot of token table it take a very long time …
dominikvitt

dominikvitt

2019-05-22 15:45

developer   ~52053

I'm closing this issue because we decided to keep all fields unencrypted until user turns on the encryption on those fields.
I'll make changes accordingly.

Issue History

Date Modified Username Field Change
2019-05-22 10:03 DenisChenu New Issue
2019-05-22 10:03 DenisChenu Status new => assigned
2019-05-22 10:03 DenisChenu Assigned To => dominikvitt
2019-05-22 10:04 DenisChenu Priority none => high
2019-05-22 10:04 DenisChenu Product Version => 4.0.0dev
2019-05-22 10:54 dominikvitt Note Added: 52029
2019-05-22 12:06 DenisChenu Note Added: 52033
2019-05-22 12:07 DenisChenu Note Edited: 52033
2019-05-22 12:44 dominikvitt Note Added: 52040
2019-05-22 12:49 DenisChenu Note Added: 52042
2019-05-22 15:45 dominikvitt Status assigned => closed
2019-05-22 15:45 dominikvitt Resolution open => no change required
2019-05-22 15:45 dominikvitt Note Added: 52053
2019-05-22 19:59 DenisChenu Relationship added related to 14874