jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Francesco Chicchiriccò (JIRA) <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-838) Avoid deprecation
Date Thu, 05 Mar 2015 17:20:38 GMT

    [ https://issues.apache.org/jira/browse/JCLOUDS-838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14349118#comment-14349118
] 

Francesco Chicchiriccò commented on JCLOUDS-838:
------------------------------------------------

Played a bit with your sample, got couple of questions:
 # is it fine to introduce an additional dependency (BouncyCastle) in order to "stop using
KeyStore of at all possible and definitely the local filesystem"?
 # shall we keep supporting PKCS12 (with password) and certificate + private key (only PEM)?

> Avoid deprecation
> -----------------
>
>                 Key: JCLOUDS-838
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-838
>             Project: jclouds
>          Issue Type: Sub-task
>          Components: jclouds-compute, jclouds-labs
>            Reporter: Francesco Chicchiriccò
>            Assignee: Francesco Chicchiriccò
>             Fix For: 2.0.0
>
>
> Two classes are marked as {{@Deprecated}} but still used:
>  * {{KeyStoreSupplier}}
>  * {{SSLContextWithKeysSupplier}}
> The TODO comment on top of both says
> {quote}
> this code needs to be completely refactored. It needs to stop using KeyStore of at all
possible and definitely the local filesystem. Please look at oauth for examples on how to
do this via PEMs.
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message