Bug 1017812

Summary:	Wrong explanation in chapter "Application Resources"
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Ladislav Thon <lthon>
Component:	Documentation	Assignee:	Zach Rhoads <zrhoads>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ladislav Thon <lthon>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	jkudrnac, rdickens, zrhoads
Target Milestone:	post-GA	Keywords:	Documentation
Target Release:	EAP 6.4.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:	Build Name: 14874, Administration and Configuration Guide-6.2-1 Build Date: 10-10-2013 14:56:59 Topic ID: 23146-541286 [Latest]
Last Closed:	2015-10-20 12:51:54 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1013506

Description Ladislav Thon 2013-10-10 14:39:40 UTC

Title: Application Resources

Describe the issue:

The text says that "by default no resource types are enabled as application resources", which is not true. Deployments are by default enabled as application resources. The issue here is that the text is not considering deployments to be resources, which I believe is wrong. For example, you can revoke the permissions to deployments from Deployer in the same way you can grant permissions to other resources.

Suggestions for improvement:

I suggest counting deployments as normal resources (which they actually are). This would of course span more [sub]chapters than just this one.

Comment 1 Ladislav Thon 2013-10-10 15:02:29 UTC

One of the other chapters that would be affected is the "Role Permissions Matrix". Specifically, the note "[1]" would need to be reworded.

Comment 3 Jakub Cechacek 2014-04-18 08:34:38 UTC

The part of the docs mentioned by lthon in original report seems to be reworked, can you confirm?

If this is ready for QE please change the status appropriately

Comment 11 Ladislav Thon 2015-07-29 14:10:04 UTC

It's been almost two years since I filed this bug, so verifying it was a bit complicated, but yes, the content has been rewritten in a way that addresses this bug.

Verified against:

- Security Guide, Revision 6.4.0-11
- How To Configure Server Security, accessed on Customer Portal 2015-07-29 (no revision number available)