Details
-
Quality Risk
-
Resolution: Done
-
Major
-
7.1.1
-
None
-
Documentation (Ref Guide, User Guide, etc.), Release Notes
-
Low
Description
Visibility should only apply to whether a table/model shows up in the system tables and should have nothing to do with whether it can be accessed.
If a designer user wants to make a model non-accessable with the ease of the visibility mechansim, then they should create a data role ("default") that does not have permissions for model. Our roles would then need a boolean attribute (any-authenticated) to denote that any authenticated user has the role.
Designer/JOPR will also need to add support for the "any-authenticated" attribute.
Attachments
Issue Links
- is related to
-
TEIIDDES-590 Add the notion of "All Users" check box to Data Role Editor which sets "any-authentication" attribute to TRUE and disables "Mapped Role Names" panel.
- Closed
- relates to
-
TEIIDDES-520 Designer permits VDB to have no visible models - at least one should be visible
- Closed
-
TEIIDDES-590 Add the notion of "All Users" check box to Data Role Editor which sets "any-authentication" attribute to TRUE and disables "Mapped Role Names" panel.
- Closed