<div dir="ltr"><div>I forgot to close loop on this. I managed to solve this problem with a config change in /etc/swift/proxy-server.conf:</div><div>I needed to include the line:</div><div>auth_version = 3</div><div> under [filter:s3token]<br><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jun 1, 2018 at 5:02 PM, Shyam Prasad N <span dir="ltr"><<a href="mailto:nspmangalore@gmail.com" target="_blank">nspmangalore@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi Kota, <br></div><div><br></div><div>I tried with the changes you suggested. It gives me the old error again...<br>eightkpc@objectstore1:~/<wbr>s3curl$ ./<a href="http://s3curl.pl" target="_blank">s3curl.pl</a> --debug --id=testerks -- <a href="http://s3server:8080" target="_blank">http://s3server:8080</a><br>s3curl: Found the url: host=s3server; port=8080; uri=; query=;<br>s3curl: s3server<br>s3curl: s3server<br>s3curl: ordinary endpoint signing case<br>s3curl: StringToSign='GET\n\n\nFri, 01 Jun 2018 11:31:50 +0000\n/'<br>s3curl: exec curl -v -H 'Date: Fri, 01 Jun 2018 11:31:50 +0000' -H 'Authorization: AWS 76498e1413284b9d961d452db608df<wbr>f4:<wbr>X1vdAhaZ4KyuM5LpMVc21ZQaGuA=' -L -H 'content-type: ' <a href="http://s3server:8080" target="_blank">http://s3server:8080</a><br>* Rebuilt URL to: <a href="http://s3server:8080/" target="_blank">http://s3server:8080/</a><span class=""><br>* Trying 20.20.20.229...<br>* TCP_NODELAY set<br>* Connected to s3server (20.20.20.229) port 8080 (#0)<br></span>> GET / HTTP/1.1<span class=""><br>> Host: s3server:8080<br>> User-Agent: curl/7.58.0<br>> Accept: */*<br></span>> Date: Fri, 01 Jun 2018 11:31:50 +0000<br>> Authorization: AWS 76498e1413284b9d961d452db608df<wbr>f4:<wbr>X1vdAhaZ4KyuM5LpMVc21ZQaGuA=<br>> <br>< HTTP/1.1 403 Forbidden<br>< x-amz-id-2: txbdd2940942ce49509226d-<wbr>005b112ea6<br>< x-amz-request-id: txbdd2940942ce49509226d-<wbr>005b112ea6<br>< Content-Type: application/xml<br>< X-Trans-Id: txbdd2940942ce49509226d-<wbr>005b112ea6<br>< X-Openstack-Request-Id: txbdd2940942ce49509226d-<wbr>005b112ea6<br>< Date: Fri, 01 Jun 2018 11:31:50 GMT<br>< Transfer-Encoding: chunked<span class=""><br>< <br><?xml version='1.0' encoding='UTF-8'?><br></span>* Connection #0 to host s3server left intact<br><Error><Code><wbr>SignatureDoesNotMatch</Code><<wbr>Message>The request signature we calculated does not match the signature you provided. Check your key and signing method.</Message><RequestId><wbr>txbdd2940942ce49509226d-<wbr>005b112ea6</RequestId></Error><br></div></div><div class="gmail_extra"><div><div class="h5"><br><div class="gmail_quote">On Fri, Jun 1, 2018 at 1:31 PM, Kota TSUYUZAKI <span dir="ltr"><<a href="mailto:tsuyuzaki.kota@lab.ntt.co.jp" target="_blank">tsuyuzaki.kota@lab.ntt.co.jp</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Shyam,<br>
<span><br>
<br>
> s3curl: StringToSign='PUT\n\n\nFri, 01 Jun 2018 05:47:53<br>
> +0000\n/s3server/testbucket'<br>
<br>
</span>It looks like your StringToSign doesn't include correct info for your request.(e.g. resource should be only "/testbucket")<br>
See <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-header-based-auth.html" rel="noreferrer" target="_blank">https://docs.aws.amazon.com/Am<wbr>azonS3/latest/API/sig-v4-heade<wbr>r-based-auth.html</a> for more info.<br>
<br>
Your request should be:<br>
<span><br>
> * Connected to s3server (20.20.20.229) port 8080 (#0)<br>
>> PUT /testbucket HTTP/1.1<br>
>> Host: s3server:8080<br>
>> User-Agent: curl/7.58.0<br>
>> Accept: */*<br>
>> Date: Fri, 01 Jun 2018 05:47:53 +0000<br>
>> Authorization: AWS<br>
> 76498e1413284b9d961d452db608df<wbr>f4:uzQs5hJOnwY4dyFk0PIxHHwmVcA<wbr>=<br>
>> Content-Length: 0<br>
<br>
</span>then, the string to sign should include the info corretly.<br>
<br>
Looking at s3curl code, it looks to fall into cname case?<br>
<br>
<a href="https://github.com/scality/S3/blob/master/tests/functional/s3curl/s3curl.pl#L311-L328" rel="noreferrer" target="_blank">https://github.com/scality/S3/<wbr>blob/master/tests/functional/s<wbr>3curl/s3curl.pl#L311-L328</a><br>
<br>
Once I played with s3curl the request with ordinary endpoint signing case worked correctly.<br>
Again, I'm not an expert of s3curl so no idea why your setting went to the cname case tho.<br>
<br>
Best,<br>
Kota<br>
<div class="m_8667295517779126777HOEnZb"><div class="m_8667295517779126777h5"><br>
(2018/06/01 14:49), Shyam Prasad N wrote:<br>
> Hi Kota,<br>
> <br>
> Thanks for the response.<br>
> When I specify the URL as <a href="http://s3server:8080/testbucket" rel="noreferrer" target="_blank">http://s3server:8080/testbucke<wbr>t</a>, it throws back a<br>
> SignatureDoesNotMatch error.<br>
> <br>
> eightkpc@objectstore1:~/s3curl<wbr>$ ./<a href="http://s3curl.pl" rel="noreferrer" target="_blank">s3curl.pl</a> --debug --id=testerks<br>
> --createBucket -- <a href="http://s3server:8080/testbucket" rel="noreferrer" target="_blank">http://s3server:8080/testbucke<wbr>t</a><br>
> s3curl: Found the url: host=s3server; port=8080; uri=/testbucket; query=;<br>
> s3curl: cname endpoint signing case<br>
> s3curl: StringToSign='PUT\n\n\nFri, 01 Jun 2018 05:47:53<br>
> +0000\n/s3server/testbucket'<br>
> s3curl: exec curl -v -H 'Date: Fri, 01 Jun 2018 05:47:53 +0000' -H<br>
> 'Authorization: AWS<br>
> 76498e1413284b9d961d452db608df<wbr>f4:uzQs5hJOnwY4dyFk0PIxHHwmVcA<wbr>=' -L -H<br>
> 'content-type: ' --data-binary -X PUT <a href="http://s3server:8080/testbucket" rel="noreferrer" target="_blank">http://s3server:8080/testbucke<wbr>t</a><br>
> * Trying 20.20.20.229...<br>
> * TCP_NODELAY set<br>
> * Connected to s3server (20.20.20.229) port 8080 (#0)<br>
>> PUT /testbucket HTTP/1.1<br>
>> Host: s3server:8080<br>
>> User-Agent: curl/7.58.0<br>
>> Accept: */*<br>
>> Date: Fri, 01 Jun 2018 05:47:53 +0000<br>
>> Authorization: AWS<br>
> 76498e1413284b9d961d452db608df<wbr>f4:uzQs5hJOnwY4dyFk0PIxHHwmVcA<wbr>=<br>
>> Content-Length: 0<br>
>><br>
> < HTTP/1.1 403 Forbidden<br>
> < x-amz-id-2: tx5c2ac9ea26a046ac96e4d-005b10<wbr>de09<br>
> < x-amz-request-id: tx5c2ac9ea26a046ac96e4d-005b10<wbr>de09<br>
> < Content-Type: application/xml<br>
> < X-Trans-Id: tx5c2ac9ea26a046ac96e4d-005b10<wbr>de09<br>
> < X-Openstack-Request-Id: tx5c2ac9ea26a046ac96e4d-005b10<wbr>de09<br>
> < Date: Fri, 01 Jun 2018 05:47:53 GMT<br>
> < Transfer-Encoding: chunked<br>
> * HTTP error before end of send, stop sending<br>
> <<br>
> <?xml version='1.0' encoding='UTF-8'?><br>
> * Closing connection 0<br>
> <Error><Code>SignatureDoesNotM<wbr>atch</Code><Message>The request signature we<br>
> calculated does not match the signature you provided. Check your key and<br>
> signing<br>
> method.</Message><RequestId>tx<wbr>5c2ac9ea26a046ac96e4d-005b10de<wbr>09</RequestId></Error><br>
> <br>
> Regards,<br>
> Shyam<br>
> <br>
> On Fri, Jun 1, 2018 at 11:02 AM, Kota TSUYUZAKI <<br>
> <a href="mailto:tsuyuzaki.kota@lab.ntt.co.jp" target="_blank">tsuyuzaki.kota@lab.ntt.co.jp</a>> wrote:<br>
> <br>
>> Hi Shyam,<br>
>><br>
>> You should specify the path starts from bucket. It will be like<br>
>><br>
>> <a href="http://20.20.20.229:8080/testBucket" rel="noreferrer" target="_blank">http://20.20.20.229:8080/testB<wbr>ucket</a><br>
>><br>
>> assuming you didn't configure virtual-hosted style.<br>
>> Even if your *Swift* endpoint is <a href="http://20.20.20.229:8080/v1/AUTH_" rel="noreferrer" target="_blank">http://20.20.20.229:8080/v1/AU<wbr>TH_</a><br>
>> dc86f7d8787b46158268bd77098b65<wbr>78,<br>
>> swift3 doesn't require the account in the path so far as well as actual<br>
>> amazon s3.<br>
>><br>
>> Best,<br>
>> Kota<br>
>><br>
>> (2018/05/31 21:33), Shyam Prasad N wrote:<br>
>>> Hi Yuxin,<br>
>>><br>
>>> Thank you for sharing your configs.<br>
>>> So I've managed to get past the Signature not matching error.<br>
>>><br>
>>> Now the error is different. InvalidbucketName:<br>
>>><br>
>>> eightkpc@objectstore1:~/s3curl<wbr>$ ./<a href="http://s3curl.pl" rel="noreferrer" target="_blank">s3curl.pl</a> --debug --id=testerks<br>
>>> --createBucket --<br>
>>> <a href="http://20.20.20.229:8080/v1/AUTH_dc86f7d8787b46158268bd77098b65" rel="noreferrer" target="_blank">http://20.20.20.229:8080/v1/AU<wbr>TH_dc86f7d8787b46158268bd77098<wbr>b65</a><br>
>> 78/testBucket<br>
>>> s3curl: Found the url: host=20.20.20.229; port=8080;<br>
>>> uri=/v1/AUTH_dc86f7d8787b46158<wbr>268bd77098b6578/testBucket; query=;<br>
>>> s3curl: cname endpoint signing case<br>
>>> s3curl: StringToSign='PUT\n\n\nThu, 31 May 2018 12:02:57 +0000\n/<br>
>>> <a href="http://20.20.20.229/v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket" rel="noreferrer" target="_blank">20.20.20.229/v1/AUTH_dc86f7d87<wbr>87b46158268bd77098b6578/<wbr>testBucket</a>'<br>
>>> s3curl: exec curl -v -H 'Date: Thu, 31 May 2018 12:02:57 +0000' -H<br>
>>> 'Authorization: AWS<br>
>>> 76498e1413284b9d961d452db608df<wbr>f4:jj/kaAEuX/vK+WUTvZyDQUUEGV0<wbr>=' -L -H<br>
>>> 'content-type: ' --data-binary -X PUT<br>
>>> <a href="http://20.20.20.229:8080/v1/AUTH_dc86f7d8787b46158268bd77098b65" rel="noreferrer" target="_blank">http://20.20.20.229:8080/v1/AU<wbr>TH_dc86f7d8787b46158268bd77098<wbr>b65</a><br>
>> 78/testBucket<br>
>>> * Trying 20.20.20.229...<br>
>>> * TCP_NODELAY set<br>
>>> * Connected to 20.20.20.229 (20.20.20.229) port 8080 (#0)<br>
>>>> PUT /v1/AUTH_dc86f7d8787b46158268b<wbr>d77098b6578/testBucket HTTP/1.1<br>
>>>> Host: <a href="http://20.20.20.229:8080" rel="noreferrer" target="_blank">20.20.20.229:8080</a><br>
>>>> User-Agent: curl/7.58.0<br>
>>>> Accept: */*<br>
>>>> Date: Thu, 31 May 2018 12:02:57 +0000<br>
>>>> Authorization: AWS<br>
>>> 76498e1413284b9d961d452db608df<wbr>f4:jj/kaAEuX/vK+WUTvZyDQUUEGV0<wbr>=<br>
>>>> Content-Length: 0<br>
>>>><br>
>>> < HTTP/1.1 400 Bad Request<br>
>>> < x-amz-id-2: tx18266052d5044eb2a3bc7-005b0f<wbr>e471<br>
>>> < x-amz-request-id: tx18266052d5044eb2a3bc7-005b0f<wbr>e471<br>
>>> < Content-Type: application/xml<br>
>>> < X-Trans-Id: tx18266052d5044eb2a3bc7-005b0f<wbr>e471<br>
>>> < X-Openstack-Request-Id: tx18266052d5044eb2a3bc7-005b0f<wbr>e471<br>
>>> < Date: Thu, 31 May 2018 12:02:57 GMT<br>
>>> < Transfer-Encoding: chunked<br>
>>> * HTTP error before end of send, stop sending<br>
>>> <<br>
>>> <?xml version='1.0' encoding='UTF-8'?><br>
>>> * Closing connection 0<br>
>>> <Error><Code>InvalidBucketName<wbr></Code><Message>The specified bucket is<br>
>> not<br>
>>> valid.</Message><RequestId>tx1<wbr>8266052d5044eb2a3bc7-<br>
>> 005b0fe471</RequestId><BucketN<wbr>ame>v1</BucketName></<br>
>> Error>eightkpc@objectstore1:~/<wbr>s3curl$<br>
>>><br>
>>><br>
>>> My specified endpoint is<br>
>>> <a href="http://20.20.20.229:8080/v1/AUTH_dc86f7d8787b46158268bd77098b6578" rel="noreferrer" target="_blank">http://20.20.20.229:8080/v1/AU<wbr>TH_dc86f7d8787b46158268bd77098<wbr>b6578</a><br>
>>> What am I doing wrong?<br>
>>><br>
>>> Regards,<br>
>>> Shyam<br>
>>><br>
>>> On Wed, May 30, 2018 at 7:32 PM, Yuxin Wang <<a href="mailto:wang.yuxin@ostorage.com.cn" target="_blank">wang.yuxin@ostorage.com.cn</a>><br>
>>> wrote:<br>
>>><br>
>>>> Hi Shyam,<br>
>>>><br>
>>>> No problem. The output of the commands is attached.<br>
>>>><br>
>>>> And my test cluster is on Swift v2.15.1 with Swift3 v1.12<br>
>>>><br>
>>>> Also, here is the common process when I'm creating an S3 credential and<br>
>>>> using in s3curl. Hope it helps.<br>
>>>><br>
>>>> 1. Create a user and a project, and assign a proper role.<br>
>>>><br>
>>>> openstack project create testproject<br>
>>>> openstack user create testuser --password 123<br>
>>>> openstack role add --project testproject --user testuser _member_<br>
>>>><br>
>>>> 2. Check accessibility to swift<br>
>>>><br>
>>>> create a test-openrc file with above info<br>
>>>> source test-openrc<br>
>>>> swift list<br>
>>>><br>
>>>> 3.Create a credential<br>
>>>><br>
>>>> openstack credential create --type ec2 --project testproject testuser<br>
>>>> '{"access": "testaccess", "secret": "testsecret"}'<br>
>>>><br>
>>>> 4. Use it in s3curl<br>
>>>><br>
>>>> add the endpoint url to `my @endpoints` in <a href="http://s3curl.pl" rel="noreferrer" target="_blank">s3curl.pl</a><br>
>>>> add the credential to .s3curl config file<br>
>>>><br>
>>>> do `<a href="http://s3curl.pl" rel="noreferrer" target="_blank">s3curl.pl</a> -i cred_name --debug -- <a href="http://endpoint" rel="noreferrer" target="_blank">http://endpoint</a> -X GET`<br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>> 在 2018年5月25日，18:17，Shyam Prasad N <<a href="mailto:nspmangalore@gmail.com" target="_blank">nspmangalore@gmail.com</a>> 写道：<br>
>>>><br>
>>>> Hi Yuxin,<br>
>>>><br>
>>>> If you don't mind, can you share the output of the following commands in<br>
>>>> your running swift3 setup?<br>
>>>><br>
>>>> openstack credential list<br>
>>>> openstack ec2 credentials list<br>
>>>> cat /etc/swift/proxy-server.conf<br>
>>>><br>
>>>> Also, what are the access keys and secret keys that you use?<br>
>>>> I want to make sure that I'm not missing anything in configuration.<br>
>>>><br>
>>>> Regards,<br>
>>>> Shyam<br>
>>>><br>
>>>> On Fri, May 25, 2018 at 3:05 PM, Shyam Prasad N <<a href="mailto:nspmangalore@gmail.com" target="_blank">nspmangalore@gmail.com</a><br>
>>><br>
>>>> wrote:<br>
>>>><br>
>>>>> Tried that. Unfortunately same error.<br>
>>>>> Is there anything I can do to troubleshoot this?<br>
>>>>><br>
>>>>> On Fri, May 25, 2018 at 2:56 PM, Yuxin Wang <<br>
>> <a href="mailto:wang.yuxin@ostorage.com.cn" target="_blank">wang.yuxin@ostorage.com.cn</a>><br>
>>>>> wrote:<br>
>>>>><br>
>>>>>> They can be any strings.<br>
>>>>>><br>
>>>>>> Replace them with whatever you want.<br>
>>>>>><br>
>>>>>> - Yuxin<br>
>>>>>><br>
>>>>>> 在 2018年5月25日，14:57，Shyam Prasad N <<a href="mailto:nspmangalore@gmail.com" target="_blank">nspmangalore@gmail.com</a>> 写道：<br>
>>>>>><br>
>>>>>> Thanks. I'll try this.<br>
>>>>>> But what values do I use in place of ak and sk? I want to use some<br>
>>>>>> command to get those values, right?<br>
>>>>>><br>
>>>>>> On Fri, May 25, 2018 at 9:52 AM, Yuxin Wang <<br>
>> <a href="mailto:wang.yuxin@ostorage.com.cn" target="_blank">wang.yuxin@ostorage.com.cn</a>><br>
>>>>>> wrote:<br>
>>>>>><br>
>>>>>>> I created ec2 credentials using command `openstack credential<br>
>> create`.<br>
>>>>>>><br>
>>>>>>> i.e.<br>
>>>>>>><br>
>>>>>>> openstack credential create --type ec2 --project proj user<br>
>> '{"access":<br>
>>>>>>> "ak", "secret": "sk”}'<br>
>>>>>>><br>
>>>>>>><br>
>>>>>>> It seems the two credentials are not the same thing.<br>
>>>>>>><br>
>>>>>>> Ref:<br>
>>>>>>><br>
>>>>>>> <a href="https://www.ibm.com/support/knowledgecenter/en/STXKQY_4.1.1/" rel="noreferrer" target="_blank">https://www.ibm.com/support/kn<wbr>owledgecenter/en/STXKQY_4.1.1/</a><br>
>>>>>>> com.ibm.spectrum.scale.v4r11.a<wbr>dv.doc/bl1adv_ConfigureOpensta<br>
>>>>>>> ckEC2credentials.htm<br>
>>>>>>> <<a href="https://nam05.safelinks.protection.outlook.com/?url=" rel="noreferrer" target="_blank">https://nam05.safelinks.prote<wbr>ction.outlook.com/?url=</a><br>
>> https%3A%2F%<a href="http://2Fwww.ibm.com" rel="noreferrer" target="_blank">2Fwww.ibm.com</a>%2Fsu<wbr>pport%2Fknowledgecenter%<br>
>> 2Fen%2FSTXKQY_4.1.1%2Fcom.ibm.<wbr>spectrum.scale.v4r11.adv.doc%2<wbr>Fbl1adv_<br>
>> ConfigureOpenstackEC2credentia<wbr>ls.htm&data=02%7C01%7C%<br>
>> 7Cc6d4af73a0fd4208f9ac08d5c20f<wbr>0a30%7C84df9e7fe9f640afb435aaa<wbr>aaaaa<br>
>> aaaa%7C1%7C0%7C636628292198191<wbr>185&sdata=cBwi02p2zc3db3%<wbr>2Bp8PDvrgAZ2%<br>
>> 2FkqjB6wnuW%2FEt0zWPA%3D&reser<wbr>ved=0><br>
>>>>>>><br>
>>>>>>> 在 2018年5月25日，10:32，Shyam Prasad N <<a href="mailto:nspmangalore@gmail.com" target="_blank">nspmangalore@gmail.com</a>> 写道：<br>
>>>>>>><br>
>>>>>>> Yes, I did.<br>
>>>>>>> I don't think this is s3curl related issue, because I tried with<br>
>> python<br>
>>>>>>> AWS SDK, and got the same error.<br>
>>>>>>><br>
>>>>>>> On Fri, May 25, 2018, 07:42 Yuxin Wang <<a href="mailto:wang.yuxin@ostorage.com.cn" target="_blank">wang.yuxin@ostorage.com.cn</a>><br>
>>>>>>> wrote:<br>
>>>>>>><br>
>>>>>>>> Did you add 127.0.0.1 to the endpoint list in <a href="http://s3curl.pl" rel="noreferrer" target="_blank">s3curl.pl</a><br>
>>>>>>>> <<a href="https://nam05.safelinks.protection.outlook.com/?url=" rel="noreferrer" target="_blank">https://nam05.safelinks.prote<wbr>ction.outlook.com/?url=</a><br>
>> http%3A%2F%2Fs3curl.pl%2F&data<wbr>=02%7C01%7C%7Cc6d4af73a0fd4208<wbr>f9ac08d5c20f<br>
>> 0a30%7C84df9e7fe9f640afb435aaa<wbr>aaaaaaaaa%7C1%7C0%<br>
>> 7C636628292198191185&sdata=nr9<wbr>HL8HskZJ8OwCfpuU2pKg7%<br>
>> 2FPnzWhTD1b4wEi02o5A%3D&reserv<wbr>ed=0><br>
>>>>>>>> ?<br>
>>>>>>>><br>
>>>>>>>> i.e.<br>
>>>>>>>><br>
>>>>>>>> my @endpoints = (‘127.0.0.1’);<br>
>>>>>>>><br>
>>>>>>>> 在 2018年5月24日，19:48，Shyam Prasad N <<a href="mailto:nspmangalore@gmail.com" target="_blank">nspmangalore@gmail.com</a>> 写道：<br>
>>>>>>>><br>
>>>>>>>> Hi,<br>
>>>>>>>><br>
>>>>>>>> I've been trying to get swift3 to work for several days now. But I<br>
>>>>>>>> haven't managed to get it running.<br>
>>>>>>>> Both with tempauth and keystoneauth, I'm getting the same error:<br>
>>>>>>>><br>
>>>>>>>> eightkpc@objectstore1:~/s3curl<wbr>$ ./<a href="http://s3curl.pl" rel="noreferrer" target="_blank">s3curl.pl</a><br>
>>>>>>>> <<a href="https://eur03.safelinks.protection.outlook.com/?url=" rel="noreferrer" target="_blank">https://eur03.safelinks.prote<wbr>ction.outlook.com/?url=</a><br>
>> http%3A%2F%2Fs3curl.pl&data=02<wbr>%7C01%7C%7C39742b8c6bf847ee381<wbr>508d5c16d1b21%<br>
>> 7C84df9e7fe9f640afb435aaaaaaaa<wbr>aaaa%7C1%7C0%7C636627596701206<wbr>160&sdata=<br>
>> lZmKF41unLVD9J1ALYUv8Vkab448NO<wbr>eGmcWcR56Rgxs%3D&reserved=0><br>
>>>>>>>> --id=testerks -- <a href="http://127.0.0.1:8080/" rel="noreferrer" target="_blank">http://127.0.0.1:8080/</a><br>
>>>>>>>> <<a href="https://eur03.safelinks.protection.outlook.com/?url=" rel="noreferrer" target="_blank">https://eur03.safelinks.prote<wbr>ction.outlook.com/?url=</a><br>
>> http%3A%2F%2F127.0.0.1%3A8080%<wbr>2F&data=02%7C01%7C%<br>
>> 7C39742b8c6bf847ee381508d5c16d<wbr>1b21%7C84df9e7fe9f640afb435aaa<wbr>aaaaa<br>
>> aaaa%7C1%7C0%7C636627596701206<wbr>160&sdata=CEHEVR1HSpK0ehQ8mmOB<wbr>A7fmjQsu7v<br>
>> jqKZda3NYVDWQ%3D&reserved=0><br>
>>>>>>>> <?xml version='1.0' encoding='UTF-8'?><br>
>>>>>>>> <Error><Code>SignatureDoesNotM<wbr>atch</Code><Message>The request<br>
>>>>>>>> signature we calculated does not match the signature you provided.<br>
>> Check<br>
>>>>>>>> your key and signing method.</Message><RequestId>tx<br>
>>>>>>>> a691e7ca97a44d56bc4c2-005b06a2<wbr>92</RequestId></Error><br>
>>>>>>>><br>
>>>>>>>> May 24 11:31:30 localhost proxy-server: 127.0.0.1 127.0.0.1<br>
>>>>>>>> 24/May/2018/11/31/30 GET / HTTP/1.0 403 - curl/7.58.0 - - 277 -<br>
>>>>>>>> txa691e7ca97a44d56bc4c2-005b06<wbr>a292 - 0.0200 - -<br>
>> 1527161490.543112040<br>
>>>>>>>> 1527161490.563107014 -<br>
>>>>>>>> May 24 11:31:30 localhost proxy-server: STDERR: 127.0.0.1 - -<br>
>>>>>>>> [24/May/2018 11:31:30] "GET / HTTP/1.1" 403 621 0.021979 (txn:<br>
>>>>>>>> txa691e7ca97a44d56bc4c2-005b06<wbr>a292)<br>
>>>>>>>><br>
>>>>>>>> eightkpc@objectstore1:~$ cat .s3curl<br>
>>>>>>>> %awsSecretAccessKeys = (<br>
>>>>>>>> tester => {<br>
>>>>>>>> id => 'test:tester',<br>
>>>>>>>> key => 'testing',<br>
>>>>>>>> },<br>
>>>>>>>> testerks => {<br>
>>>>>>>> id => 'e6289a1b5692461388d0597a4873d<wbr>054',<br>
>>>>>>>> key => '88bb706887094696b082f008ba133<wbr>ad7',<br>
>>>>>>>> },<br>
>>>>>>>> );<br>
>>>>>>>><br>
>>>>>>>> eightkpc@objectstore1:~$ openstack ec2 credentials show<br>
>>>>>>>> e6289a1b5692461388d0597a4873d0<wbr>54<br>
>>>>>>>> +------------+----------------<wbr>------------------------------<br>
>>>>>>>> ------------------------------<wbr>------------------------------<br>
>>>>>>>> --------------------------+<br>
>>>>>>>> | Field | Value<br>
>>>>>>>><br>
>>>>>>>> |<br>
>>>>>>>> +------------+----------------<wbr>------------------------------<br>
>>>>>>>> ------------------------------<wbr>------------------------------<br>
>>>>>>>> --------------------------+<br>
>>>>>>>> | access | e6289a1b5692461388d0597a4873d0<br>
>>>>>>>> 54<br>
>>>>>>>> |<br>
>>>>>>>> | links | {u'self': u'<a href="http://controller:5000/v3/us" rel="noreferrer" target="_blank">http://controller:5000/v3/us</a><br>
>>>>>>>> ers/d7df7b56343b4ea988869fc30e<wbr>feda09/credentials/OS-EC2/e628<br>
>>>>>>>> 9a1b5692461388d0597a4873d054'} |<br>
>>>>>>>> | project_id | dc86f7d8787b46158268bd77098b65<br>
>>>>>>>> 78<br>
>>>>>>>> |<br>
>>>>>>>> | secret | 88bb706887094696b082f008ba133a<br>
>>>>>>>> d7<br>
>>>>>>>> |<br>
>>>>>>>> | trust_id | None<br>
>>>>>>>><br>
>>>>>>>> |<br>
>>>>>>>> | user_id | d7df7b56343b4ea988869fc30efeda<br>
>>>>>>>> 09<br>
>>>>>>>> |<br>
>>>>>>>> +------------+----------------<wbr>------------------------------<br>
>>>>>>>> ------------------------------<wbr>------------------------------<br>
>>>>>>>> --------------------------+<br>
>>>>>>>><br>
>>>>>>>> Can someone please let me know what is going on?<br>
>>>>>>>><br>
>>>>>>>> Regards,<br>
>>>>>>>> Shyam<br>
>>>>>>>> <proxy-server.conf>___________<wbr>______________________________<wbr>______<br>
>>>>>>>> Mailing list: <a href="https://eur03.safelinks.protection.outlook.com/?url=" rel="noreferrer" target="_blank">https://eur03.safelinks.protec<wbr>tion.outlook.com/?url=</a><br>
>>>>>>>> http%3A%2F%<a href="http://2Flists.openstack.org" rel="noreferrer" target="_blank">2Flists.openstack.o<wbr>rg</a>%2Fcgi-bin%2Fmailman%<br>
>>>>>>>> 2Flistinfo%2Fopenstack&data=02<wbr>%7C01%7C%7C39742b8c6bf847ee3<br>
>>>>>>>> 81508d5c16d1b21%7C84df9e7fe9f6<wbr>40afb435aaaaaaaa<br>
>>>>>>>> aaaa%7C1%7C0%7C636627596701206<wbr>160&sdata=KI%2F2T2FhVQJTeX1KbI<br>
>>>>>>>> ObDZVDiUA3SbTq6Pplo1bc7ak%3D&r<wbr>eserved=0<br>
>>>>>>>> Post to : <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a><br>
>>>>>>>> Unsubscribe : <a href="https://eur03.safelinks.protection.outlook.com/?url=" rel="noreferrer" target="_blank">https://eur03.safelinks.protec<wbr>tion.outlook.com/?url=</a><br>
>>>>>>>> http%3A%2F%<a href="http://2Flists.openstack.org" rel="noreferrer" target="_blank">2Flists.openstack.o<wbr>rg</a>%2Fcgi-bin%2Fmailman%<br>
>>>>>>>> 2Flistinfo%2Fopenstack&data=02<wbr>%7C01%7C%7C39742b8c6bf847ee3<br>
>>>>>>>> 81508d5c16d1b21%7C84df9e7fe9f6<wbr>40afb435aaaaaaaa<br>
>>>>>>>> aaaa%7C1%7C0%7C636627596701206<wbr>160&sdata=KI%2F2T2FhVQJTeX1KbI<br>
>>>>>>>> ObDZVDiUA3SbTq6Pplo1bc7ak%3D&r<wbr>eserved=0<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>><br>
>>>>>><br>
>>>>>><br>
>>>>>> --<br>
>>>>>> -Shyam<br>
>>>>>> ______________________________<wbr>_________________<br>
>>>>>> Mailing list: <a href="https://nam05.safelinks.protection.outlook.com/?url=" rel="noreferrer" target="_blank">https://nam05.safelinks.protec<wbr>tion.outlook.com/?url=</a><br>
>>>>>> http%3A%2F%<a href="http://2Flists.openstack.org" rel="noreferrer" target="_blank">2Flists.openstack.o<wbr>rg</a>%2Fcgi-bin%2Fmailman%<br>
>>>>>> 2Flistinfo%2Fopenstack&data=02<wbr>%7C01%7C%7Cc6d4af73a0fd4208f<br>
>>>>>> 9ac08d5c20f0a30%7C84df9e7fe9f6<wbr>40afb435aaaaaaaa<br>
>>>>>> aaaa%7C1%7C0%7C636628292198347<wbr>486&sdata=tGhHmhX%2By9RVFjl%<br>
>>>>>> 2B31%2BVgRiN1mD%2Fc%2B7QLiImlG<wbr>nCv98%3D&reserved=0<br>
>>>>>> Post to : <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a><br>
>>>>>> Unsubscribe : <a href="https://nam05.safelinks.protection.outlook.com/?url=" rel="noreferrer" target="_blank">https://nam05.safelinks.protec<wbr>tion.outlook.com/?url=</a><br>
>>>>>> http%3A%2F%<a href="http://2Flists.openstack.org" rel="noreferrer" target="_blank">2Flists.openstack.o<wbr>rg</a>%2Fcgi-bin%2Fmailman%<br>
>>>>>> 2Flistinfo%2Fopenstack&data=02<wbr>%7C01%7C%7Cc6d4af73a0fd4208f<br>
>>>>>> 9ac08d5c20f0a30%7C84df9e7fe9f6<wbr>40afb435aaaaaaaa<br>
>>>>>> aaaa%7C1%7C0%7C636628292198347<wbr>486&sdata=tGhHmhX%2By9RVFjl%<br>
>>>>>> 2B31%2BVgRiN1mD%2Fc%2B7QLiImlG<wbr>nCv98%3D&reserved=0<br>
>>>>>><br>
>>>>>><br>
>>>>>><br>
>>>>><br>
>>>>><br>
>>>>> --<br>
>>>>> -Shyam<br>
>>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>> --<br>
>>>> -Shyam<br>
>>>> ______________________________<wbr>_________________<br>
>>>> Mailing list: <a href="https://nam05.safelinks.protection.outlook.com/?url=" rel="noreferrer" target="_blank">https://nam05.safelinks.protec<wbr>tion.outlook.com/?url=</a><br>
>>>> http%3A%2F%<a href="http://2Flists.openstack.org" rel="noreferrer" target="_blank">2Flists.openstack.o<wbr>rg</a>%2Fcgi-bin%2Fmailman%<br>
>>>> 2Flistinfo%2Fopenstack&data=02<wbr>%7C01%7C%7C7bf3d25a540b4d402d3<wbr>d08d5c22a<br>
>> 5c90%<br>
>>>> 7C84df9e7fe9f640afb435aaaaaaaa<wbr>aaaa%7C1%7C0%7C636628409546910<wbr>462&sdata=%<br>
>>>> 2FhXb5bRIU0kCZSDj4pJXfEkVYEtBA<wbr>pcA6OjhKHw1fMQ%3D&reserved=0<br>
>>>> Post to : <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a><br>
>>>> Unsubscribe : <a href="https://nam05.safelinks.protection.outlook.com/?url=" rel="noreferrer" target="_blank">https://nam05.safelinks.protec<wbr>tion.outlook.com/?url=</a><br>
>>>> http%3A%2F%<a href="http://2Flists.openstack.org" rel="noreferrer" target="_blank">2Flists.openstack.o<wbr>rg</a>%2Fcgi-bin%2Fmailman%<br>
>>>> 2Flistinfo%2Fopenstack&data=02<wbr>%7C01%7C%7C7bf3d25a540b4d402d3<wbr>d08d5c22a<br>
>> 5c90%<br>
>>>> 7C84df9e7fe9f640afb435aaaaaaaa<wbr>aaaa%7C1%7C0%7C636628409546910<wbr>462&sdata=%<br>
>>>> 2FhXb5bRIU0kCZSDj4pJXfEkVYEtBA<wbr>pcA6OjhKHw1fMQ%3D&reserved=0<br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> ______________________________<wbr>_________________<br>
>>> Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/</a><br>
>> openstack<br>
>>> Post to : <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a><br>
>>> Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/</a><br>
>> openstack<br>
>>><br>
>><br>
>><br>
>><br>
>><br>
> <br>
> <br>
<br>
<br>
</div></div></blockquote></div><br><br clear="all"><br></div></div><span class="HOEnZb"><font color="#888888">-- <br><div class="m_8667295517779126777gmail_signature" data-smartmail="gmail_signature">-Shyam</div>
</font></span></div>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">-Shyam</div>
</div>