You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Timothy A. Bish (Jira)" <ji...@apache.org> on 2025/03/05 17:52:00 UTC
[jira] [Commented] (PROTON-2874) [protonj2] Add TrustManagerFactory option to client SslOptions
[ https://issues.apache.org/jira/browse/PROTON-2874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17932707#comment-17932707 ]
Timothy A. Bish commented on PROTON-2874:
-----------------------------------------
You can provide your own SSLContext via the sslContextOverride option in which you can configure the key and trust managers as you like and use your custom version.
> [protonj2] Add TrustManagerFactory option to client SslOptions
> ---------------------------------------------------------------
>
> Key: PROTON-2874
> URL: https://issues.apache.org/jira/browse/PROTON-2874
> Project: Qpid Proton
> Issue Type: Improvement
> Components: protonj2
> Affects Versions: protonj2-1.0.0-M23
> Reporter: Tomáš Kukosa
> Assignee: Timothy A. Bish
> Priority: Minor
>
> SslOptions accept various trust store locations but I have custom TrustManagerFactory not related to any single persistent store location.
> It would be nice to have possibility to set it into SslOptions.
> The SslSupport.loadTrustManagerFactory() could use it directly if has been set.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org