[
https://jira.jboss.org/browse/TEIIDDES-514?page=com.atlassian.jira.plugin...
]
John Verhaeg commented on TEIIDDES-514:
---------------------------------------
First, it seems like your attached mock-up is far too simplistic in that it wouldn't
allow us to show enough information (based on what's available in the schema).
I really think we need to discuss the expected users of this feature. I keep hearing that
it's completely different people that administer security than those that do the
modeling, and the security people would probably feel pretty overwhelmed at having to
navigate the Designer just to apply data policies.
Given that's true, I'd suggest we provide a different perspective with a different
set of views for this (maybe just one initially to satisfy time constraints). The view(s)
could be vdb- or policy-centric and use either tree or table widgets. We'd show VDB,
model, table, column, data policy (and it's description), permission, and CRUD
settings. It probably even makes sense to display the mapped roles, too.
Create Data Policy Wizard/Editor launched from VDB Editor
---------------------------------------------------------
Key: TEIIDDES-514
URL:
https://jira.jboss.org/browse/TEIIDDES-514
Project: Teiid Designer
Issue Type: Task
Components: Editors, VDB & Execution
Affects Versions: 7.1
Reporter: Barry LaFond
Assignee: Barry LaFond
Priority: Critical
Fix For: 7.1
Attachments: VdbDataPolicyPanel.jpg
1) Data Policies are VDB-centric.
2) There can be ZERO or more data policies within a VDB.
3) A data policy can define permissions (CRUD) on models, tables and columns that span
"Models".
A) VDB Editor needs to provide some Data Policy access on the basic editor page. Maybe
the "User Files" bottom group is broken up into two panels, the RIGHT panel
being "Data Policies". Panel would allow "ADD", and
"REMOVE", but also "EDIT" buttons.
Create a Wizard that can CREATE AND EDIT a data policy.
Wizard/Dialog should be able to Select any of the models contained in the VDB (that allow
entitlements. Maybe just relational?)
- Contain an Editable "Name" field.
- Contain an Editable "Role Name" field.
- Contain a Tree-Table with contents of selected Model AND 4 checkboxes to handle
CRUD values
- Enablement of CRUD check-boxes should be driven from "Supports Updates"
values for both Virtual and Physical relational table data.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira