Bug 1234240

Summary:	[QE] Fix JACC and XACML relation
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Josef Cacek <jcacek>
Component:	Documentation	Assignee:	Russell Dickenson <rdickens>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Josef Cacek <jcacek>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.4.0	CC:	eap-docs, jtymel, rdickens, zrhoads
Target Milestone:	post-GA
Target Release:	EAP 6.4.1
Hardware:	Unspecified
OS:	Unspecified
URL:	https://access.stage.redhat.com/beta/documentation/en/red-hat-jboss-enterprise-application-platform-64-security-architecture
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-10-20 12:59:01 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:	1233489

Description Josef Cacek 2015-06-22 07:38:11 UTC

Book: Security Architecture
Revision: n_1415923_security-architecture_version_6.4_edition_1.0_release_0-revision_1
Section: JACC

Issue description:
There is a sentence about JACC and XACML relation in the guide: 
"In addition to providing security for web applications and EJBs, JACC provides fine grained authorization using XACML."

This is not correct. The JACC and the XACML are 2 different and independent authorization types.

Suggestions for improvement:
Remove the sentence.

Comment 6 Jan Tymel 2015-08-04 10:57:51 UTC

Verified in revision "n_1583811_security-architecture_version_6.4_edition_1.0_release_0-revision_6712191" of https://access.stage.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-6.4/security-architecture