Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Blocker
Fix Version/s: 7.1.0.DR18
Affects Version/s: 7.1.0.DR10
Component/s: Management, Security
Labels:

CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Target Release:

7.1.0.GA
Git Pull Request:
https://github.com/wildfly/wildfly-core/pull/2398
Steps to Reproduce:
Hide

SSLMasterSlaveOneWayTestCase

SSLMasterSlaveTwoWayTestCase

How to setup EAP for this scenario is described in documentation
https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/how-to-configure-server-security/#configure-ssl-managed-domain
Show
SSLMasterSlaveOneWayTestCase SSLMasterSlaveTwoWayTestCase How to setup EAP for this scenario is described in documentation https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/how-to-configure-server-security/#configure-ssl-managed-domain

SFDC Cases Counter:
SFDC Cases Links:

This is regression against EAP 7.0 . Customers relying on this feature won't be able to migrate to EAP 7.1.

Working configuration of TLS between domain and host controller from EAP 7.0 (legacy) does not work on EAP 7.1 anymore.
In server log there is this error:

server.log

[Host Controller] Caused by: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
[Host Controller] 	at org.jboss.remoting3.remote.ClientConnectionOpenListener$StartTls.handleEvent(ClientConnectionOpenListener.java:527)
[Host Controller] 	at org.jboss.remoting3.remote.ClientConnectionOpenListener$StartTls.handleEvent(ClientConnectionOpenListener.java:477)
[Host Controller] 	at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
[Host Controller] 	at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
[Host Controller] 	at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
[Host Controller] 	at org.xnio.nio.WorkerThread.run(WorkerThread.java:567)
[Host Controller] 	at ...asynchronous invocation...(Unknown Source)
[Host Controller] 	at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:466)
[Host Controller] 	at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:437)
[Host Controller] 	at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:430)
[Host Controller] 	at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:163)
[Host Controller] 	at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:119)
[Host Controller] 	... 9 more

See attached server.log for context log.

Tests in wildfly-core covering this scenario are currently ignored:

SSLMasterSlaveOneWayTestCase is ignored by ~~WFCORE-1978~~
SSLMasterSlaveTwoWayTestCase is ignored by ~~WFCORE-2068~~

- - Sort By Name
  - Sort By Date
  - Ascending
  - Descending
  - Thumbnails
  - List
  - Download All

server.log
55 kB
2017/01/09 2:55 AM

is blocked by

JBEAP-10809 Upgrade Remoting to 5.0.0.Beta22

Verified

is cloned by

WFCORE-2521 TLS between domain and host controllers does not work

Resolved

is incorporated by

JBEAP-10508 (7.1.0) Upgrade to WildFly Core to 3.0.0.Beta21

Verified

is related to

JBEAP-10245 HTTPSConnectionWithCLITestCase and HTTPSManagementInterfaceTestCase Failing Due To Native Protocol Issue

Verified

WFCORE-2068 HTTPSConnectionWithCLITestCase and HTTPSManagementInterfaceTestCase Failing Due To Native Protocol Issue

Resolved

WFCORE-1978 Add support for client cert authentication in domain mode.

Resolved

(1 is related to)

Assignee:: Darran Lofthouse

Reporter:: Martin Choma

Tester:: Martin Choma

QA Contact:: Martin Choma

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: 2017/01/09 2:56 AM

Updated:: 2020/09/14 5:31 AM

Resolved:: 2017/05/11 4:38 AM

Details

Description

Attachments

Attachments

Issue Links

Activity

People

Dates