Project

General

Profile

Actions
Copy link

Task #198

closed

EAV form - implement confidential properties

Added by Radek Tomiška over 7 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Radek Tomiška
Category:
Eav
Target version:
Beryl
Start date:
11/22/2016
Due date:
% Done:

100%

Estimated time:
12.00 h
Owner:

Description

Confidential properties will be saved as "guarded strings" and wil not be sent to fe. Fe will only know, when value is filled and value could be changed. New feature ConfidentialStorage will be created (api only + default implementation in standard database).

Actions
Copy link
 #1

Updated by Radek Tomiška over 7 years ago

  • Description updated (diff)
  • Status changed from New to In Progress
  • Estimated time changed from 8.00 h to 12.00 h
Actions
Copy link
 #2

Updated by Radek Tomiška over 7 years ago

  • Status changed from In Progress to Needs feedback
  • Assignee changed from Radek Tomiška to Vít Švanda
  • % Done changed from 0 to 90

I've created confidential storage api with default "naive" implementation as database table. Test and documentation (https://proj.bcvsolutions.eu/ngidm/doku.php?id=navrh:confidential-storage) is included.

ConfidentialStorage is used now for:
  • storing identity's password
  • storing confidential eav properties (with connector properties)

Could you make a review and test, please?

Actions
Copy link
 #3

Updated by Vít Švanda over 7 years ago

  • Status changed from Needs feedback to Closed
  • Assignee changed from Vít Švanda to Radek Tomiška
  • % Done changed from 90 to 100

I tested this very deeply during integration extended attribute to provisioning. Wroks fine

Actions
Copy link

Also available in: Atom PDF