[
https://issues.apache.org/jira/browse/QPID-7402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15837818#comment-15837818
]
Keith Wall commented on QPID-7402:
----------------------------------
Is the use case for development? If so, I think we should add a alternative
initial-config that defines a self signed certificate and two ports: HTTP
serving both PLAIN/TLS and AMQP serving both PLAIN/TLS. I think separately
there should be a 'production' initial config that defines only TLS are refers
to key material via system properties.
> [Java Broker] https in default config
> -------------------------------------
>
> Key: QPID-7402
> URL: https://issues.apache.org/jira/browse/QPID-7402
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Lorenz Quack
> Fix For: qpid-java-7.0
>
>
> Currently the broker ships with a default config that has a plain HTTP port
> configured.
> Since basic auth over HTTP is disabled by default there is no way to remotely
> configure the broker out of the box.
> I suggest to modify the default config to add a authprovider with self-signed
> certificate and either replace the existing HTTP port or add a new HTTPS port.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
