Loading...

XML

Word

Printable

Details

Type: Task
Resolution: Done
Priority: Blocker
Fix Version/s: 8.0.0.Final
Affects Version/s: None
Component/s: Management, Remoting, Security
Labels:
None

Description

Need to double check the behaviour here, the wrapping of Remoting so far it leaving the Remoting specific messages as-is - need to verify we are not double encrypting the connection and also the Client Cert based authentication requirements on that connection.

Attachments

Sub-Tasks

1.	Add support for aliases to be defined in the jboss-cli.xml for connection settings.	Closed	Darran Lofthouse
2.	bin]$ ./jboss-cli.sh -c --controller=localhost:9999 - Results in Connection Timed Out	Closed	Darran Lofthouse
3.	Connecting using https-remoting times out and leaves thread within CLI spinning at 100%	Closed	Darran Lofthouse
4.	Re-review CLI server certificate acceptance.	Closed	Darran Lofthouse
5.	connect https-remoting://localhost:9990 in CLI provides no feedback to indicate SSL not in use.	Closed	Darran Lofthouse
6.	CLI over HTTP should switch to / be redirected to https automatically.	Closed	Darran Lofthouse
7.	NullPointerException in RemotingHttpUpgradeService if no http port.	Closed	Darran Lofthouse
8.	CLI Unable to connect using https-remoting address.	Closed	Darran Lofthouse
9.	http-interface is used instead of native-interface for native access	Closed	Darran Lofthouse
10.	Add meaningful error message when http-remoting is used in CLI against server that does not support it.	Closed	Darran Lofthouse
11.	Deprecate old CLI connection based methods	Closed	Darran Lofthouse
12.	CLI can not connect to the server started with port-offset	Closed	Darran Lofthouse

Activity

People

Assignee:: Darran Lofthouse

Reporter:: Darran Lofthouse

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 2013/06/27 5:54 AM

Updated:: 2017/12/06 11:40 AM

Resolved:: 2014/01/30 6:43 AM