Bug 1314914 - Security information is not consolidated
Summary: Security information is not consolidated
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Documentation
Version: 6.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER4
: 7.0.0
Assignee: Christian Huffman
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-04 20:40 UTC by dereed
Modified: 2019-01-30 19:52 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-30 19:52:04 UTC
Type: Bug


Attachments (Terms of Use)

Description dereed 2016-03-04 20:40:15 UTC
Document URL: 
https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Data_Grid/6.6/html-single/Security_Guide/index.html#sect-Hot_Rod_Interface_Security
https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Data_Grid/6.6/html-single/Administration_and_Configuration_Guide/index.html#sect-Memcached_Interface_Security

Section Number and Name: 
Security Guide - 2.6.6. Hot Rod Interface Security
Security Guide - 2.6.7. User Authentication over Hot Rod Using SASL
Admin Guide - 11.7. REST Interface Security
Admin Guide - 12.4. Memcached Interface Security

Describe the issue: 
Information on securing JDG remote interfaces is spread out, in multiple documents.
Depending on which interface you're trying to secure and which document you look at, you'll either find the information, or not even a reference.

This will likely lead customers to believe an interface cannot be secured, when there are details for other interfaces in that document, but not even a reference to securing that interface.

Suggestions for improvement: 
The documentation for securing Hot Rod, REST, and memcached should all be in the same area of the same document.  A link should be included in the other document in the relevant section.

Additional information:

Comment 3 Christian Huffman 2019-01-30 19:52:04 UTC
Closing this out due to age. If the issue persists please file a corresponding JIRA.


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