Feature #7997
Encryption for client storage data / registry
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
Related issues
History
#1 Updated by Galya B 6 months ago
- Related to Feature #4854: origin affinity added
#2 Updated by Galya B 6 months 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 6 months 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.