Bug 1238945

Summary: [QE] Auth modules documentation should describe hierarchy of the modules
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Hynek Mlnarik <hmlnarik>
Component: DocumentationAssignee: Zach Rhoads <zrhoads>
Status: CLOSED CURRENTRELEASE QA Contact: Pavel Slavicek <pslavice>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.4.0CC: eap-docs, pslavice
Target Milestone: post-GA   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://access.stage.redhat.com/beta/documentation/en/red-hat-jboss-enterprise-application-platform-64-login-module-reference
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-20 12:47:11 UTC Type: Enhancement
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: 1089155, 1233012    

Description Hynek Mlnarik 2015-07-03 06:40:18 UTC 
Revision: n_1416293__version__edition__release_-revision_1 (initial)

Issue description:
The guide on login modules lists authentication/authorization modules and their options. The current format in the guide - plain list - does not reflect the module hierarchy, i.e. that module A is a descendant of module B, and hence has all options of module B, only appends few more own options upon those of B.

Suggested improvement:
It would be easier to understand, maintain and verify the module options if the notion of hierarchy was there. Then only additional options of the child module would be necessary to describe instead of repeating all options of the parent.