JetS3t did not have explicit support for temporary/session-based AWS
accounts. I have now added this support via the new
AWSSessionCredentials class, see the changeset here:
https://bitbucket.org/jmurty/jets3t/changeset/7a4f742d991d
If you are able to check out the latest version of the JetS3 code and
try out this new credential type that would be great.
If you are not able to use the latest code, you can work around the
lack of explicit support by using the existing AWSDevPayCredentials
class, since the session-based accounts use the same
"x-amz-security-token" HTTP header as the supported DevPay mechanism.
Construct an AWSDevPayCredentials instance setting the access key and
secret key as usual, set the user token value to your session key, and
leave the product token as null. This should result in JetS3t sending
your session token value with all requests, as required when using
this authentication mechanism.
Hope this helps,
James
> --
> You received this message because you are subscribed to the Google Groups "JetS3t Users" group.
> To post to this group, send email to jets3t...@googlegroups.com.
> To unsubscribe from this group, send email to jets3t-users...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/jets3t-users?hl=en.
>
But if not, hopefully the workaround will suffice.