jclouds-notifications mailing list archives

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

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

Ignasi Barrera commented on JCLOUDS-838:

While the API does not implement another authentication mechanism than HTTPS client auth,
a possible workaround would be to use a custom KeyManager (an in-memory one, for example),
and configure the KeyStore to use it.

This gist contains a working example using the Azure SDK, but could easily be adapted and
extended to work with jclouds.

> 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ò
>             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

View raw message