Back to bug 1021607

Who When What Removed Added
Dana Mison 2013-12-04 03:03:54 UTC Doc Text Some resources are non-addressable to server-group and host scoped roles in order to provide a simplified view of the management model to improve usability. This is distinct from resources that are non-addressable to protect sensitive data.

For server-group scoped roles this means that resources in the `profile`, `socket binding group`, `deployment`, `deployment override`, `server group`, `server config` and `server` portions of the management model will not be visible if they are not related to the server-groups specified for the role.

For host-scoped roles this means that resources in the `/host=*` portion of the management model will not be visible if they are not related to the server groups specified for the role.

However in some cases this simplified view can hide information that while it is outside the scope of what the user is managing, it can provide guidance to the user as to a course of action. An example of this is http://bugzilla.redhat.com/show_bug.cgi?id=1015524[BZ# 1015524].

In a future release, some of these non-addressable resources might be changed to be addressable but read-only. This will not affect the security of the server because they were not non-addressable for security reasons. Red Hat recommends that you do not rely on the non-addressability of resources to hide information unless the non-addressability is defined in a sensitivity constraint.
Doc Type Bug Fix Known Issue
Dana Mison 2013-12-04 07:01:46 UTC Doc Text Some resources are non-addressable to server-group and host scoped roles in order to provide a simplified view of the management model to improve usability. This is distinct from resources that are non-addressable to protect sensitive data.

For server-group scoped roles this means that resources in the `profile`, `socket binding group`, `deployment`, `deployment override`, `server group`, `server config` and `server` portions of the management model will not be visible if they are not related to the server-groups specified for the role.

For host-scoped roles this means that resources in the `/host=*` portion of the management model will not be visible if they are not related to the server groups specified for the role.

However in some cases this simplified view can hide information that while it is outside the scope of what the user is managing, it can provide guidance to the user as to a course of action. An example of this is http://bugzilla.redhat.com/show_bug.cgi?id=1015524[BZ# 1015524].

In a future release, some of these non-addressable resources might be changed to be addressable but read-only. This will not affect the security of the server because they were not non-addressable for security reasons. Red Hat recommends that you do not rely on the non-addressability of resources to hide information unless the non-addressability is defined in a sensitivity constraint.
Some resources are non-addressable to server-group and host scoped roles in order to provide a simplified view of the management model to improve usability. This is distinct from resources that are non-addressable to protect sensitive data.

For server-group scoped roles this means that resources in the `profile`, `socket binding group`, `deployment`, `deployment override`, `server group`, `server config` and `server` portions of the management model will not be visible if they are not related to the server-groups specified for the role.

For host-scoped roles this means that resources in the `/host=*` portion of the management model will not be visible if they are not related to the server groups specified for the role.

However in some cases this simplified view can hide information that while it is outside the scope of what the user is managing, it can provide guidance to the user as to a course of action. An example of this is http://bugzilla.redhat.com/show_bug.cgi?id=1015524[BZ# 1015524].

In a future release, some of these non-addressable resources might be changed to be addressable but non-readable. This will not affect the security of the server because they were not non-addressable for security reasons. Red Hat recommends that you do not rely on the non-addressability of resources to hide information unless the non-addressability is defined in a sensitivity constraint.
Tom WELLS 2014-02-11 05:01:18 UTC Keywords Documentation, FutureFeature, Triaged
CC twells
John Doyle 2014-02-13 19:36:09 UTC CC jdoyle
Tom WELLS 2014-05-15 05:34:34 UTC Keywords Triaged
Ladislav Thon 2014-05-15 08:12:52 UTC Flags needinfo?(brian.stansberry)
Brian Stansberry 2014-05-15 12:41:44 UTC Flags needinfo?(brian.stansberry)
Tom WELLS 2014-05-19 01:15:44 UTC Assignee rdickens eap-docs
Nikoleta Hlavickova 2014-05-22 11:01:08 UTC Target Release --- EAP 6.3.0
CC nziakova
Dana Mison 2014-05-27 01:29:52 UTC CC dmison
Scott Mumford 2014-05-29 03:24:48 UTC CC smumford
Summary RBAC: Explain the two kinds of non-addressability that we have [Doc Change] RBAC: Explain the two kinds of non-addressability that we have
Russell Dickenson 2014-06-12 03:42:36 UTC Status NEW ASSIGNED
CC rdickens
Assignee eap-docs rdickens
Russell Dickenson 2014-06-16 04:45:18 UTC Status ASSIGNED POST
Scott Mumford 2014-07-01 04:37:01 UTC Keywords Documentation, FutureFeature
Component doc-Administration_and_Configuration_Guide doc-Release_Notes
Assignee rdickens smumford
Scott Mumford 2014-07-01 04:41:02 UTC Status POST MODIFIED
Scott Mumford 2014-07-02 01:07:14 UTC Priority unspecified high
Vladimir Dosoudil 2014-07-04 11:41:48 UTC Status MODIFIED ON_QA
Target Milestone --- ER9
Ladislav Thon 2014-07-07 12:02:28 UTC Status ON_QA ASSIGNED
Scott Mumford 2014-07-08 23:21:03 UTC Status ASSIGNED POST
Scott Mumford 2014-07-15 04:41:32 UTC Status POST ON_QA
Ladislav Thon 2014-07-15 06:43:07 UTC Status ON_QA ASSIGNED
Scott Mumford 2014-07-16 21:34:33 UTC Comment 19 is private 1 0
Ladislav Thon 2014-07-25 15:11:12 UTC Status ASSIGNED POST
Tom WELLS 2014-08-14 12:48:56 UTC Component doc-Release_Notes Documentation
Ladislav Thon 2014-08-14 13:02:36 UTC Flags needinfo?(twells)
Ladislav Thon 2014-08-15 07:05:14 UTC Flags needinfo?(twells)
Tom WELLS 2014-09-29 01:30:40 UTC Keywords Documentation, Triaged
Target Milestone ER9 post-GA
Scott Mumford 2014-11-30 23:46:59 UTC Status POST CLOSED
Resolution --- CURRENTRELEASE
Last Closed 2014-11-30 18:46:59 UTC
Ladislav Thon 2014-12-01 08:56:38 UTC Flags needinfo?(smumford)
Ladislav Thon 2015-01-23 07:42:34 UTC Flags needinfo?(brian.stansberry)
Brian Stansberry 2015-01-23 16:34:28 UTC Flags needinfo?(smumford) needinfo?(brian.stansberry)
Ladislav Thon 2015-01-26 07:22:25 UTC Flags needinfo?(smumford)
Ladislav Thon 2015-01-27 07:57:57 UTC Status CLOSED ASSIGNED
Resolution CURRENTRELEASE ---
Keywords Reopened
Jitka Kozana 2015-01-29 10:00:41 UTC CC jkudrnac
Scott Mumford 2015-02-02 02:08:52 UTC Status ASSIGNED MODIFIED
Version 6.2.0 6.4.0
Flags needinfo?(smumford)
Scott Mumford 2015-02-03 01:29:11 UTC CC dandread
Component Documentation Domain Management
Scott Mumford 2015-02-03 01:37:49 UTC Summary [Doc Change] RBAC: Explain the two kinds of non-addressability that we have [Doc Change] RBAC: The two kinds of non-addressability
Scott Mumford 2015-02-03 01:41:39 UTC Target Release EAP 6.3.0 TBD EAP 7
Scott Mumford 2015-02-03 22:55:59 UTC Group private
Scott Mumford 2015-02-23 01:31:54 UTC Status MODIFIED ON_QA
Target Release TBD EAP 7 EAP 6.4.0
Target Milestone post-GA GA
Ladislav Thon 2015-02-23 10:29:09 UTC Status ON_QA VERIFIED
John Skeoch 2015-05-18 01:31:21 UTC CC twells lcarlon
lcarlon 2015-05-19 10:17:53 UTC CC lcarlon
Scott Mumford 2015-07-03 00:50:13 UTC Status VERIFIED CLOSED
Resolution --- CURRENTRELEASE
Last Closed 2014-11-30 18:46:59 UTC 2015-07-02 20:50:13 UTC

Back to bug 1021607