October 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3933) Controller is not available using https-remoting protocol

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-3933?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-3933: -------------------------------------- Assignee: Darran Lofthouse (was: Alexey Loubyansky) > Controller is not available using https-remoting protocol > --------------------------------------------------------- > > Key: WFLY-3933 > URL: https://issues.jboss.org/browse/WFLY-3933 > Project: WildFly > Issue Type: Feature Request > Components: CLI > Environment: I am trying to deploy my war archive on 8.0.0 final jboss redhat RPM. Everything was working fine until I tried to enable my security options. I have added both <ssl> tag and <trustore> tag under SecurityRealm. In addition I added an <https-listener> and enabled the https-management console. > I've added a controller to jboss-cli.xml as follows: > <controllers> > <controller name="MyHttpsController"> > <protocol>https-remoting</protocol> > <host>myHost</host> > <port>myPort</port> > </controller> > </controllers> > I'm executing the jboss server process by runnning the standalone.sh script and then I'm trying to deploy my war by using the following line: > ./jboss-cli.sh --connect=MyHttpsController command="deploy [myWarPath]" > I get the following error: > The controller is not available at myIp:myPort: java.net.ConnectException: .....The connection timed out > I can open the https-management console via the browser and I checked that my server is actually listening to this port. Please help my if you can, this is very important. > I appreciate all help you can give me. > Thanks all, Michael > Reporter: Michael Sherman > Assignee: Darran Lofthouse > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3933) Controller is not available using https-remoting protocol

by Michael Sherman (JIRA)

Michael Sherman created WFLY-3933: ------------------------------------- Summary: Controller is not available using https-remoting protocol Key: WFLY-3933 URL: https://issues.jboss.org/browse/WFLY-3933 Project: WildFly Issue Type: Feature Request Components: CLI Environment: I am trying to deploy my war archive on 8.0.0 final jboss redhat RPM. Everything was working fine until I tried to enable my security options. I have added both <ssl> tag and <trustore> tag under SecurityRealm. In addition I added an <https-listener> and enabled the https-management console. I've added a controller to jboss-cli.xml as follows: <controllers> <controller name="MyHttpsController"> <protocol>https-remoting</protocol> <host>myHost</host> <port>myPort</port> </controller> </controllers> I'm executing the jboss server process by runnning the standalone.sh script and then I'm trying to deploy my war by using the following line: ./jboss-cli.sh --connect=MyHttpsController command="deploy [myWarPath]" I get the following error: The controller is not available at myIp:myPort: java.net.ConnectException: .....The connection timed out I can open the https-management console via the browser and I checked that my server is actually listening to this port. Please help my if you can, this is very important. I appreciate all help you can give me. Thanks all, Michael Reporter: Michael Sherman Assignee: Alexey Loubyansky -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (ELY-43) Clean up Base64

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-43?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse commented on ELY-43: ------------------------------------- FYI I believe Undertow already contains a forked implementation of this class - if we were able to adopt it within Elytron it does mean when we add a dependency on Elytron from Undertow we can remove one further Base64 fork. > Clean up Base64 > --------------- > > Key: ELY-43 > URL: https://issues.jboss.org/browse/ELY-43 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Utils > Reporter: Darran Lofthouse > Assignee: Farah Juma > Fix For: 1.0.0.Beta1 > > > The Base64 implementation has been split out of PasswordUtils some additional steps are needed to finish cleaning it up: - > - Look at switching to input and output streams instead of the custom iterators it is using. > - Consider the ByteStringBuilder from SASL > - As potentially more visible ensure clearer method names. > - Ensure adequate javadoc and cross referencing of standards supported. > e.g. If we implement an RFC ensure the number is referenced. > - Testing of each variant > - Consider optional support, e.g. decoding a padded String > - Go beyond testing we can decode what we encode and ensure pre-encoded values can be handled adequately. > Any other clean up here that seems relevant. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-83) EAR deployment overlay did not work if there is no related resource included in the ear