Shri Javadekar's profile - activity

2014-09-24 01:23:44 -0600 received badge  Taxonomist
2013-11-01 20:49:04 -0600 received badge  Self-Learner (source)
2013-11-01 20:49:04 -0600 received badge  Teacher (source)
2013-11-01 20:48:50 -0600 received badge  Student (source)
2013-05-13 16:37:36 -0600 received badge  Famous Question (source)
2013-04-08 04:15:48 -0600 received badge  Notable Question (source)
2013-04-05 13:54:08 -0600 answered a question How can I use tempurl with swift and keystoneauth.

Finally, I got the solution. You need the following in the proxy-server.conf

[filter:authtoken]

...

delay_auth_decision = 1

2013-04-03 18:53:33 -0600 commented answer How can I use tempurl with swift and keystoneauth.

On further investigations, this is what happens: getkey() doesn't find "temp-url-key/accountid" in memcache. Therefore it calls makepreauthedenv to create a new env dictionary. Calling self.app with this new env should return with x-account-meta-temp-url-key in its header. But it does not :(

2013-04-02 23:20:48 -0600 received badge  Popular Question (source)
2013-04-02 19:25:14 -0600 answered a question How can I use tempurl with swift and keystoneauth.

I have two roles on the system. admin and swiftoperator. When I do swift stat using a user whose role is swiftoperator, I can see the Meta Temp-Url-Key. But if I do swift stat using a user whose role is admin, I don't see the Meta Temp-Url-Key. Does that matter?

My app is using a user whose role is swiftoperator. So it should still be able to use tempurl right?

2013-04-02 01:44:13 -0600 commented question How can I use tempurl with swift and keystoneauth.

I'm using the jclouds library. It's been supporting tempUrls for sometime now. I believe it is doing the right thing. Here's the code: https://github.com/jclouds/jclouds/blob/master/apis/swift/src/main/java/org/jclouds/openstack/swift/blobstore/SwiftBlobSigner.java#L151

2013-04-01 16:47:16 -0600 commented answer How can I use tempurl with swift and keystoneauth.

Haah.. That seems to have done the trick for setting QUERYSTRING. However, it looks like _getkey returns None.

2013-04-01 16:46:49 -0600 answered a question How can I use tempurl with swift and keystoneauth.

Haah.. That seems to have done the trick for setting QUERYSTRING. However, it looks like _getkey returns None. Does that mean that the http request didn't send the X-Account-Meta-Temp-URL-Key in the http request?

2013-04-01 16:46:33 -0600 received badge  Supporter (source)
2013-04-01 16:08:34 -0600 asked a question How can I use tempurl with swift and keystoneauth.

I am seeing a problem where everytime I try to use a tempurl, I get an "Unauthorized: Temp URL invalid" error. I don't find enough documentation about debugging tempurls. Hence this question.

If I want to configure tempurl, do I only have to add the following in the proxy-server conf and restart it?

<proxy-server.conf>

...
pipeline = catch_errors healthcheck cache authtoken tempurl swiftauth proxy-server
...
[filter:tempurl]
use = egg:swift#tempurl

</proxy-server.conf>

If this is all that is required, I have done this. From the swift command line utility, I can see the Meta Temp-Url-Key option set on the account as well. But when I use a tempUrl, I get the Unauthorized error. I logged the actual url and it looks something like this:

http://<proxy-server-ip>:8080/v1/AUTHb3238727b1e94025b8eb38b60d1cef6b/cloud-testing/ae260ba046043710?tempurlsig=3d11cc195a89916b71c77cc9c1c7201083d9dbf9&tempurl_expires=1364923538

I verified that the value of temp-url-expires is greater than the current time on the proxy server when it receives the request.

I debugged this further by adding additional log statements in the swift code and restarting proxy. It turns out that QUERY_STRING is not getting set in the env dictionary.

Any ideas?

Thanks in advance. -Shri