Project

General

Profile

Feature #7997

Encryption for client storage data / registry

Added by Galya B over 2 years ago. Updated over 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:

Related issues

Related to User Interface - Feature #4854: origin affinity Closed
Related to User Interface - Feature #4517: optionally back the 4GL features for Registry access with the user-specific offline storage features Closed

History

#1 Updated by Galya B over 2 years ago

#2 Updated by Galya B over 2 years ago

  • Related to Feature #4517: optionally back the 4GL features for Registry access with the user-specific offline storage features added

#3 Updated by Galya B over 2 years ago

Registry is accessed in 4GL via GET-KEY-VALUE and PUT-KEY-VALUE methods. In FWD registry is backed up by different implementations listed in #4517-13. All of the implementations come with security risks and are not recommended for storing sensitive information in plain text. One of the implementations in FWD's web drivers is localStorage which is probably the least secure of them all. To improve this aspect encryption should be implemented as requested in #4854-121. The encryption should take effect in registry and client storage, which is used by registry methods, but also for enhanced browser configs and can be accessed in java for any other purposes in the future.

#4 Updated by Galya B over 2 years ago

What encryption? It should be reversible.

#5 Updated by Greg Shah over 2 years ago

Yes, and we need to decide if we would use a server-wide key or if we would implement per-account level keys.

Also available in: Atom PDF