[
https://issues.apache.org/jira/browse/JCLOUDS-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753349#comment-13753349
]
Shri Javadekar commented on JCLOUDS-196:
----------------------------------------
Jclouds is already using the secure temp_url_sig mechanism when a timeout is
passed as an argument to signGetBlob/signPutBlob. Without a timeout value, it
wouldn't be possible to use the temp_url_sig mechanism. @gaul, are you
suggesting that jclouds should use some default timeout or a timeout obtained
by a jclouds property for implementations that don't have an explicit timeout?
For the record, there are two implementations of signGetBlob which take three
arguments. One which takes the timeout as an argument and uses the temp_url_sig
mechanism. The other takes org.jclouds.blobstore.options.GetOptions as an
argument and uses the auth token. The two argument implementation also uses the
auth token.
signPutBlob only has one three argument implementation which takes a timeout
value as an argument.
> Swift signGetBlob and signPutBlob implementations differ between two- and
> three-argument calls
> ----------------------------------------------------------------------------------------------
>
> Key: JCLOUDS-196
> URL: https://issues.apache.org/jira/browse/JCLOUDS-196
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-blobstore
> Affects Versions: 1.6.1
> Reporter: Andrew Gaul
>
> The two-argument Swift signGetBlob and signPutBlob methods use the legacy
> shared secret X-Auth-Token to authenticate client requests while the
> three-argument methods use the more secure temp_url_sig mechanism. We should
> default both calls to the secure mechanism and provide a property to override
> for older Swift installations.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
