[jboss-jira] [JBoss JIRA] (AS7-3322) Need to review how the SSL port is specified for the HTTP management interface.

[ https://issues.jboss.org/browse/AS7-3322?page=com.atlassian.jira.plugin.s... ] Brian Stansberry reassigned AS7-3322: ------------------------------------- Assignee: Tomaz Cerar (was: Darran Lofthouse) [10:26am] darranl: Nihility, bstansberry it was this one - we don't have a socket binding for the HTTPS port https://issues.jboss.org/browse/AS7-3322 so it is a bit inconsistent when we enable SSL [10:32am] bstansberry: darranl: oh, we're just supporting config of the HTTP socket via a binding [10:32am] bstansberry: , not the HTTPS one [10:32am] darranl: bstansberry, the issue is that before the socket binding we have a normal port an a secure port, the socket binding works for the non secured port but we have to revert to the non socket binding to enable https - also we can't really do https on it's own as at the very least browsers should be able to connect http and be redirected [10:34am] bstansberry: darranl: assign it to me; i'll find re-assign it [10:34am] bstansberry: if there's anything tricky about it, please leave a comment in the JIRA [10:35am] bstansberry: my assumption is it's just a matter of adding the appropriate config and using it [10:35am] darranl: bstansberry, I don't think there is anything tricky - for the purpose of that Jira we just need both ports to be definable using a socket-binding and only open the ports specified [10:35am] bstansberry: darranl: cool, that should be no problem -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira