Bug 1233754 - [QE] Security domain mentioned instead of security realm
Summary: [QE] Security domain mentioned instead of security realm
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
medium
Target Milestone: ER1
: EAP 6.4.3
Assignee: David Michael
QA Contact: Ondrej Kotek
URL: https://access.stage.redhat.com/beta/...
Whiteboard:
Depends On:
Blocks: 1233494
TreeView+ depends on / blocked
 
Reported: 2015-06-19 12:52 UTC by Ondrej Lukas
Modified: 2015-10-20 04:51 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-20 04:51:55 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ondrej Lukas 2015-06-19 12:52:39 UTC
Book: How to Configure Identity Management
Revision: n_1415593_how-to-configure-identity-management-in-jboss-enterprise-application-platform-6_version_6.4_edition_1.0_release_0-revision_1
Section: 3. Reference the new security domain in the Management Interface

Issue description:
There is name of the section "Reference the new security domain in the Management Interface" and text "... that new security domain must be referenced by the management interfaces." In both cases, new "security realm" should be referenced, not "security domain".

Suggestions for improvement:
There shoud be "Reference the new security realm in the Management Interface" and "... that new security realm must be referenced by the management interfaces."

Comment 2 David Michael 2015-07-03 06:17:29 UTC
One instance is still visible "that new security domain must be referenced"

Comment 5 Jan Tymel 2015-07-31 11:27:21 UTC
Verified in revision "n_1575711_how-to-configure-identity-management_version_6.4_edition_1.0_release_0-revision_6701181" of https://access.stage.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-6.4/how-to-configure-identity-management


Note You need to log in before you can comment on or make changes to this bug.