Bug 1010790 - Mismatch between rtgov-client and server configuration - OOTB default value for client does not work with the default OOTB value for the server
Summary: Mismatch between rtgov-client and server configuration - OOTB default value f...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: Installer
Version: 6.0.0 GA
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ER4
: ---
Assignee: Thomas Hauser
QA Contact: Len DiMaggio
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-23 05:23 UTC by Jiri Pechanec
Modified: 2014-02-06 15:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)

Description Jiri Pechanec 2013-09-23 05:23:15 UTC
rt-gov client by default suggests htpps-scheme url to connect to rtgov server.

Unfrotunately rtgov server does not have https connector enabled.

Comment 1 Len DiMaggio 2013-09-26 12:59:50 UTC
Does this mean that OOTB the client config cannot connect to the server?

Comment 2 Len DiMaggio 2013-09-26 13:05:53 UTC
In other words, does the installer correctly configure the client?

Is the real problem that the default value (https) provided in the installer does not work (as the server has http configured)?

Can't we change the default value for the client to work OOTB with the server?

Comment 3 Thomas Hauser 2013-09-26 16:11:20 UTC
Need to know what the installer should do to resolve this issue.

Comment 4 Thomas Hauser 2013-09-27 18:25:02 UTC
This issue has been resolved by having http:// in the default URL rather than https://

Comment 5 Jiri Pechanec 2013-10-01 05:50:17 UTC
Unfrotunately it is not enough - it is necessary to change the default port too.

In ER4 it is set to 8443 (which is https) but should be 8080

Comment 6 Thomas Hauser 2013-10-01 13:30:24 UTC
Done.

Comment 8 Jiri Pechanec 2013-10-07 05:32:23 UTC
Verified in ER4 04-Oct-2013 04:44


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