[
https://issues.apache.org/jira/browse/DISPATCH-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15402344#comment-15402344
]
Ganesh Murthy commented on DISPATCH-446:
----------------------------------------
You should now be able to insert an sslProfile via qdmanage
{noformat}
qdmanage CREATE --type=org.apache.qpid.dispatch.sslProfile
cert-file=/home/gmurthy/opensource/dispatch/tests/config-2/server-certificate.pem
key-file=/home/gmurthy/opensource/dispatch/tests/config-2/server-private-key.pem
password=server-password name=server-ssl-profile
cert-db=/home/gmurthy/opensource/dispatch/tests/config-2/ca-certificate.pem
{noformat}
and then subsequently add a connector or listener referencing the above
sslProfile
{noformat}
qdmanage create --type=connector role=route-container addr=localhost port=10101
name=localhost.broker.10101.connector sslProfile=server-ssl-profile
(likewise try qdmanage create --type=listener)
{noformat}
The sslProfile that references any connectors/listeners cannot be deleted until
all those referencing connectors/listeners have themselves been deleted.
> Make sslProfile an entity and remove all annotations
> ----------------------------------------------------
>
> Key: DISPATCH-446
> URL: https://issues.apache.org/jira/browse/DISPATCH-446
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Container
> Affects Versions: 0.6.0
> Reporter: Ganesh Murthy
> Assignee: Ganesh Murthy
>
> Currently the sslProfile is an annotation. This prevents it from being added
> thru qdmanage. Make sslProfile an entity so that it becomes a first class
> citizen. Make sure that listener and connector referencing the sslProfile
> continues to work as before.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
