Bug 535511 (RHQ-2199)

Summary:	Remote API - Allow secure transport
Product:	[Other] RHQ Project	Reporter:	Jay Shaughnessy <jshaughn>
Component:	Communications Subsystem	Assignee:	John Mazzitelli <mazz>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.3	Keywords:	SubTask
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
URL:	http://jira.rhq-project.org/browse/RHQ-2199
Whiteboard:
Fixed In Version:	1.3	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
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:	534378

Description Jay Shaughnessy 2009-06-30 19:16:00 UTC

svn rev4097 adds a new remoting connector being deployed by the ear. it uses the servlet transport over the http port today. we will have to figure out something later to make this configurable (to allow someone to go over sslservlet port 7443 for security purposes). today, its over unsecured servlet transport , port 7080. We should probably write a subtask jira here so we remember to do this. 

we will have people that will only want to allow remote clients to go over secure transport. It may be as simple as deploying a second service (remote-api-secure-service.xml) that uses the configured https port (i.e. copy remote-api-service.xml and change the transport to sslservlet and the port to the https property).

Comment 1 John Mazzitelli 2009-09-01 19:01:04 UTC

didn't I already do this? I think you can go over port 7443 via the SSL transport now.

Comment 2 John Mazzitelli 2009-09-04 20:10:06 UTC

this was fixed by RHQ-2298 and RHQ-2301

Comment 3 Red Hat Bugzilla 2009-11-10 20:59:46 UTC

This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2199
This bug duplicates RHQ-2298
This bug is incorporated by RHQ-2301