Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1157754

Summary: SSL configuration refers to non-existent Tomcat configuration
Product: [JBoss] JBoss Operations Network Reporter: dsteigne
Component: DocumentationAssignee: Tyler Kelly <tkelly>
Status: CLOSED CURRENTRELEASE QA Contact: Prachi <pyadav>
Severity: high Docs Contact:
Priority: high    
Version: JON 3.2.3, JON 3.3.0CC: fbrychta, loleary, pyadav, theute, tkelly
Target Milestone: post-GAKeywords: Documentation, Reopened, Triaged
Target Release: JON 3.3.2   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
[Admin_Config] Moved this to 3.3.2 as it missed triage. I think the section identified by Deborah requires improvements to clarity, and updates to info from the KBase linked in the customer cases.
Last Closed: 2017-09-19 06:50:22 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: 1323876    
Bug Blocks:    

Description dsteigne 2014-10-27 15:48:49 UTC
Document URL: 
https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Operations_Network/3.2/html/Admin_and_Config/JBoss_ON_and_SSL-Authentication.html
Section Number and Name: 
4.2. Setting up Client Authentication Between Servers and Agents
Describe the issue: 
The paragraph describing how to change Tomcat:
...
".. edit the JBoss ON server's Tomcat configuration file (serverRoot/jon-server-3.2.GA/jbossas/server/default/deploy/jboss-web.deployer/server.xml to uncomment the <Connector> section which says Provides a secure but un-authenticated https connector for browsers to use. and set the port for them to use. "

This folder structure is for older JBoss ON versions, refer to the upstream documentation to make the corrections - https://docs.jboss.org/author/display/RHQ/Securing+Communications#SecuringCommunications-Authentication

Suggestions for improvement: 

Additional information:

Comment 2 Jared MORGAN 2015-02-13 03:18:07 UTC
This missed triage, and I honestly think the identified section need a deep review. The KBase linked in the Customer case has some great info specific to JON about configuring keypairs and enabling security. I'd like to review this and make sure what we're telling customers in the 3.3 guide reflects commercial reality.

Comment 4 Scott Mumford 2015-09-03 00:47:16 UTC
Taking ownership of JON docs bugs.

Comment 6 Filip Brychta 2016-02-17 11:04:36 UTC
*** Bug 1303526 has been marked as a duplicate of this bug. ***

Comment 7 Filip Brychta 2016-02-17 11:09:54 UTC
Keeping this one open because it's linked to customer cases. Moving additional info from closed bz 1303526 here:

Another problem in this section is in shown rhq-server.properties parts.
All occurrences of "${jboss.server.home.dir}/conf/" should be replaced by "${jboss.server.config.dir}/" which is default path in JON 3.3.z

Path described in JON 3.3 Documentation does not exist. It is showing for the server, copy the keystore into the serverRoot/jon-server-3.3.2.GA/jbossas/server/default/conf/ directory which is no longer available in JON 3.3 (doc-err-02)
Location should be jon-server-3.3.2.GA/jbossas/standalone/configuration/ directory

Comment 8 Filip Brychta 2016-02-17 11:20:00 UTC
There are still 2 occurrences of "jbossas/server/default/conf/" sub-path which should be replaced by "jbossas/standalone/configuration".

Full path to configuration directory should look like this "jon-server-version/jbossas/standalone/configuration/" or " <JBoss ON server Install Dir>/jbossas/standalone/configuration/"

Comment 15 Tyler Kelly 2017-09-18 03:19:06 UTC
Based on the discussion in the preceding comments, this item appears to have already been completed. Is there anything still to-do on this bug?

Comment 16 Larry O'Leary 2017-09-18 15:05:37 UTC
Based on what this BZ was reporting, yes. This issue is resolved as per https://access.redhat.com/documentation/en-us/red_hat_jboss_operations_network/3.2/html/admin_and_config/jboss_on_and_ssl-authentication

I also verified that this was done for the 3.3 guide.

I would say that this is either ready for CLOSED CURRENTRELEASE or ON_QA. I'll let that be up to you.

Comment 17 Tyler Kelly 2017-09-19 01:37:11 UTC
This looks like it should get a quick QA