Project

General

Profile

Actions
Copy link

Task #102

closed

Configuration agenda - "sec" prefix and column secured mishmash

Added by Vít Švanda over 8 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Low
Assignee:
Radek Tomiška
Category:
Configuration
Target version:
Beryl
Start date:
08/18/2016
Due date:
% Done:

100%

Estimated time:
Owner:

Description

  • In database is column secured. Same information is in prefix idm.sec.**.
  • When I created item with prefix idm.sec.** then column secured is not checked.
Actions
Copy link
 #1

Updated by Radek Tomiška about 8 years ago

  • Status changed from New to Needs feedback
  • Assignee changed from Radek Tomiška to Ondřej Kopr
  • % Done changed from 0 to 90

I've added check on name and boolean properties (secured and confidential) to BE and FE. When name is changed, then properties secured and confidential are automatically changed by naming conventions. When logged identity does not have permission to modify secured configuration, then appropriate validation message is shown.

Could you make a review and test, please?

Actions
Copy link
 #2

Updated by Ondřej Kopr about 8 years ago

  • Status changed from Needs feedback to Resolved
  • Assignee changed from Ondřej Kopr to Radek Tomiška
  • % Done changed from 90 to 100
Feedback
  • Test with user that have role with access to app configurations public - works,
  • try to add idm.sec check as confidential, not work - OK.

Everything is OK, dynamicaly change check for confidential is nice and sexy, thank you.

Actions
Copy link
 #3

Updated by Radek Tomiška about 8 years ago

  • Status changed from Resolved to Closed
Actions
Copy link

Also available in: Atom PDF