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

Andrew Gaul updated JCLOUDS-1110:
---------------------------------
    Description: 
Currently the Atmos signer uses the default expiration instead of honoring the 
user-supplied value. After fixing this testSignGetUrlWithTime, 
testSignGetUrlWithTimeExpired, testSignPutUrlWithTime, and 
testSignPutUrlWithTimeExpired from BaseBlobSignerLiveTest should succeed 
without expected UnsupportedOperationException. EMC documents the expiration 
parameter on page 67 of the Atmos 2.1 programmers guide.

[~shrinand] Would you mind addressing this?


  was:
Currently the Atmos signer uses the default expiration instead of honoring the 
user-supplied value. After fixing this testSignGetUrlWithTime, 
testSignGetUrlWithTimeExpired, testSignPutUrlWithTime, and 
testSignPutUrlWithTimeExpired from BaseBlobSignerLiveTest should succeed 
without expected UnsupportedOperationException. Microsoft documents the 
expiration parameter on page 67 of the Atmos 2.1 programmers guide.

[~shrinand] Would you mind addressing this?



> Atmos time-limited signed URLs
> ------------------------------
>
>                 Key: JCLOUDS-1110
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1110
>             Project: jclouds
>          Issue Type: New Feature
>          Components: jclouds-blobstore
>    Affects Versions: 1.9.2
>            Reporter: Andrew Gaul
>              Labels: atmos
>
> Currently the Atmos signer uses the default expiration instead of honoring 
> the user-supplied value. After fixing this testSignGetUrlWithTime, 
> testSignGetUrlWithTimeExpired, testSignPutUrlWithTime, and 
> testSignPutUrlWithTimeExpired from BaseBlobSignerLiveTest should succeed 
> without expected UnsupportedOperationException. EMC documents the expiration 
> parameter on page 67 of the Atmos 2.1 programmers guide.
> [~shrinand] Would you mind addressing this?



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

Reply via email to