You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Sebb (JIRA)" <ji...@apache.org> on 2011/03/13 19:08:59 UTC

[jira] Created: (NET-372) FTPSClient: java.security.cert.CertificateException: No X509TrustManager implementation available if trustManager == null

FTPSClient: java.security.cert.CertificateException: No X509TrustManager implementation available if trustManager == null
-------------------------------------------------------------------------------------------------------------------------

                 Key: NET-372
                 URL: https://issues.apache.org/jira/browse/NET-372
             Project: Commons Net
          Issue Type: Bug
            Reporter: Sebb


FTPSClient defaults to providing the TrustManager provided by FTPSTrustManager.

It should be possible to use setTrustManager(null) to obtain the default JVM trust manager, however this fails with

java.security.cert.CertificateException: No X509TrustManager implementation available

because SSLContext.init(KeyManager[] km, TrustManager[] tm, SecureRandom random) expects null parameters, but does not allow for null entries in the TrustManager array.

The init call needs to be changed so null is passed instead of an array with a null entry.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (NET-372) FTPSClient: java.security.cert.CertificateException: No X509TrustManager implementation available if trustManager == null

Posted by "Sebb (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/NET-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sebb updated NET-372:
---------------------

    Fix Version/s: 3.0

> FTPSClient: java.security.cert.CertificateException: No X509TrustManager implementation available if trustManager == null
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: NET-372
>                 URL: https://issues.apache.org/jira/browse/NET-372
>             Project: Commons Net
>          Issue Type: Bug
>            Reporter: Sebb
>             Fix For: 3.0
>
>
> FTPSClient defaults to providing the TrustManager provided by FTPSTrustManager.
> It should be possible to use setTrustManager(null) to obtain the default JVM trust manager, however this fails with
> java.security.cert.CertificateException: No X509TrustManager implementation available
> because SSLContext.init(KeyManager[] km, TrustManager[] tm, SecureRandom random) expects null parameters, but does not allow for null entries in the TrustManager array.
> The init call needs to be changed so null is passed instead of an array with a null entry.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Resolved: (NET-372) FTPSClient: java.security.cert.CertificateException: No X509TrustManager implementation available if trustManager == null

Posted by "Sebb (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/NET-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sebb resolved NET-372.
----------------------

    Resolution: Fixed

> FTPSClient: java.security.cert.CertificateException: No X509TrustManager implementation available if trustManager == null
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: NET-372
>                 URL: https://issues.apache.org/jira/browse/NET-372
>             Project: Commons Net
>          Issue Type: Bug
>            Reporter: Sebb
>
> FTPSClient defaults to providing the TrustManager provided by FTPSTrustManager.
> It should be possible to use setTrustManager(null) to obtain the default JVM trust manager, however this fails with
> java.security.cert.CertificateException: No X509TrustManager implementation available
> because SSLContext.init(KeyManager[] km, TrustManager[] tm, SecureRandom random) expects null parameters, but does not allow for null entries in the TrustManager array.
> The init call needs to be changed so null is passed instead of an array with a null entry.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira