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

Bug 1279556

Summary: remove 'TLS' value from rhq.server.tomcat.security.secure-socket-protocol property references
Product: [JBoss] JBoss Operations Network Reporter: Marc Shirley <mshirley>
Component: DocumentationAssignee: Scott Mumford <smumford>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact: Scott Mumford <smumford>
Priority: urgent    
Version: JON 3.3.4CC: fbrychta, loleary, smumford
Target Milestone: post-GA   
Target Release: ---   
Hardware: Unspecified   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-25 00:23:51 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:

Description Marc Shirley 2015-11-09 17:42:43 UTC
Document URL: 
https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Operations_Network/3.3/html/Admin_and_Config/configuring-ssl.html#JBoss_ON_and_SSL-Encryption

Section Number and Name: 
4.1 "Setting up Encryption", Item 1.e. "Optionally, define the secure protocol to use."

Describe the issue: 
'TLS' is no longer a valid value for the rhq.server.tomcat.security.secure-socket-protocol property and so should be modified in the example.  It is valid for the rhq.server.client.security.secure-socket-protocol, so that value can stay the same like in the below example.

Suggestions for improvement: 
rhq.server.tomcat.security.secure-socket-protocol=TLSv1,TLSv1.1,TLSv1.2
rhq.server.client.security.secure-socket-protocol=TLS

Additional information:

Comment 1 Larry O'Leary 2016-01-27 18:27:43 UTC
*** Bug 1302330 has been marked as a duplicate of this bug. ***