Bug 1370489 - Missing sslservlet variant in description of Client Authentication Between Servers and Agents
Summary: Missing sslservlet variant in description of Client Authentication Between Se...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Documentation
Version: JON 3.3.6
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: ---
Assignee: Scott Mumford
QA Contact: Filip Brychta
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-26 13:09 UTC by Filip Brychta
Modified: 2016-09-05 04:16 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-05 04:16:05 UTC
Type: Bug


Attachments (Terms of Use)

Description Filip Brychta 2016-08-26 13:09:59 UTC
Document URL: 
https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Operations_Network/3.3/html/Admin_and_Config/JBoss_ON_and_SSL-Authentication.html

Section Number and Name: 
Step 8. - Enable client authentication

Describe the issue: 
It's not clear that it's describing configuration for sslsocket


Suggestions for improvement: 
Original text:
rhq.communications.connector.security.client-auth-mode parameter to need and the rhq.server.client.security.server-auth-mode-enabled parameter to true.
Set the information about the keystore and truststore files.
All of the configuration for incoming messages (agent-to-server communications) is set in rhq.communications.connector.security.* parameters. The configuration for outgoing messages is set in rhq.server.client.security.* parameters. 

Improvement:
rhq.communications.connector.security.client-auth-mode parameter to need and the rhq.server.client.security.server-auth-mode-enabled parameter to true when using sslsocket. When using sslservlet set rhq.server.tomcat.security.client-auth-mode parameter to true and the rhq.server.client.security.server-auth-mode-enabled parameter to true.

Set the information about the keystore and truststore files.
All of the configuration for incoming messages (agent-to-server communications when using sslsocket) is set in rhq.communications.connector.security.* parameters. The configuration for outgoing messages is set in rhq.server.client.security.* parameters. 


Additional information:


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