Bug 1234240 - [QE] Fix JACC and XACML relation
Summary: [QE] Fix JACC and XACML relation
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Documentation
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: post-GA
: EAP 6.4.1
Assignee: Russell Dickenson
QA Contact: Josef Cacek
URL: https://access.stage.redhat.com/beta/...
Whiteboard:
Depends On:
Blocks: 1233489
TreeView+ depends on / blocked
 
Reported: 2015-06-22 07:38 UTC by Josef Cacek
Modified: 2015-10-20 12:59 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-20 12:59:01 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

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
Note You need to log in before you can comment on or make changes to this bug.