[ 
https://issues.apache.org/jira/browse/PROTON-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell updated PROTON-1447:
-----------------------------------
    Affects Version/s:     (was: 0.15.0)
                       proton-j-0.18.0
             Priority: Major  (was: Blocker)
        Fix Version/s: proton-j-0.19.0

Rob has made an initial change to address this, if youd like to give it a try 
before the next release [[email protected]].

Similar to my comment in PROTON-1449, you could also use PROTON-1405 now to 
allow providing multiple certificates.

> Unable to provide multiple certificates using setTrustedCaDb
> ------------------------------------------------------------
>
>                 Key: PROTON-1447
>                 URL: https://issues.apache.org/jira/browse/PROTON-1447
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-j
>    Affects Versions: proton-j-0.18.0
>         Environment: JDK 1.8.0_121
>            Reporter: Priyanka Mathur
>            Assignee: Rob Godfrey
>             Fix For: proton-j-0.19.0
>
>
> Using 
> http://qpid.apache.org/releases/qpid-proton-0.9.1/proton/java/api/org/apache/qpid/proton/engine/impl/ssl/SslDomainImpl.html#setTrustedCaDb(java.lang.String)
>  to set the certificate will work only on the top most certificate provided 
> in the input stream because readCertificate from SslEngineFacadeFactory.java 
> uses generateCertificate which gets only the first certificate that holds 
> between "-----BEGIN CERTIFICATE-----" and "-----END CERTIFICATE-----". If 
> more than one are provided then you either need to loop and take one at a 
> time calling generateCertificate or use generateCertificates. Please provide 
> a fix for this asap as this is blocking our roll out of further certificates. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to