Re: [Openstack] Struggling to get the s3 api interface to work with swift.

[Shyam Prasad N]

I forgot to close loop on this. I managed to solve this problem with a
config change in /etc/swift/proxy-server.conf:
I needed to include the line:
auth_version = 3
under [filter:s3token]


On Fri, Jun 1, 2018 at 5:02 PM, Shyam Prasad N 
wrote:

> Hi Kota,
>
> I tried with the changes you suggested. It gives me the old error again...
> eightkpc@objectstore1:~/s3curl$ ./s3curl.pl --debug --id=testerks --
> http://s3server:8080
> s3curl: Found the url: host=s3server; port=8080; uri=; query=;
> s3curl: s3server
> s3curl: s3server
> s3curl: ordinary endpoint signing case
> s3curl: StringToSign='GET\n\n\nFri, 01 Jun 2018 11:31:50 +\n/'
> s3curl: exec curl -v -H 'Date: Fri, 01 Jun 2018 11:31:50 +' -H
> 'Authorization: AWS 
> 76498e1413284b9d961d452db608dff4:X1vdAhaZ4KyuM5LpMVc21ZQaGuA='
> -L -H 'content-type: ' http://s3server:8080
> * Rebuilt URL to: http://s3server:8080/
> *   Trying 20.20.20.229...
> * TCP_NODELAY set
> * Connected to s3server (20.20.20.229) port 8080 (#0)
> > GET / HTTP/1.1
> > Host: s3server:8080
> > User-Agent: curl/7.58.0
> > Accept: */*
> > Date: Fri, 01 Jun 2018 11:31:50 +
> > Authorization: AWS 76498e1413284b9d961d452db608dff4:
> X1vdAhaZ4KyuM5LpMVc21ZQaGuA=
> >
> < HTTP/1.1 403 Forbidden
> < x-amz-id-2: txbdd2940942ce49509226d-005b112ea6
> < x-amz-request-id: txbdd2940942ce49509226d-005b112ea6
> < Content-Type: application/xml
> < X-Trans-Id: txbdd2940942ce49509226d-005b112ea6
> < X-Openstack-Request-Id: txbdd2940942ce49509226d-005b112ea6
> < Date: Fri, 01 Jun 2018 11:31:50 GMT
> < Transfer-Encoding: chunked
> <
> 
> * Connection #0 to host s3server left intact
> SignatureDoesNotMatchThe request signature
> we calculated does not match the signature you provided. Check your key and
> signing method.txbdd2940942ce49509226d-
> 005b112ea6
>
> On Fri, Jun 1, 2018 at 1:31 PM, Kota TSUYUZAKI <
> tsuyuzaki.k...@lab.ntt.co.jp> wrote:
>
>> Hi Shyam,
>>
>>
>> > s3curl: StringToSign='PUT\n\n\nFri, 01 Jun 2018 05:47:53
>> > +\n/s3server/testbucket'
>>
>> It looks like your StringToSign doesn't include correct info for your
>> request.(e.g. resource should be only "/testbucket")
>> See https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-heade
>> r-based-auth.html for more info.
>>
>> Your request should be:
>>
>> > * Connected to s3server (20.20.20.229) port 8080 (#0)
>> >> PUT /testbucket HTTP/1.1
>> >> Host: s3server:8080
>> >> User-Agent: curl/7.58.0
>> >> Accept: */*
>> >> Date: Fri, 01 Jun 2018 05:47:53 +
>> >> Authorization: AWS
>> > 76498e1413284b9d961d452db608dff4:uzQs5hJOnwY4dyFk0PIxHHwmVcA=
>> >> Content-Length: 0
>>
>> then, the string to sign should include the info corretly.
>>
>> Looking at s3curl code, it looks to fall into cname case?
>>
>> https://github.com/scality/S3/blob/master/tests/functional/s
>> 3curl/s3curl.pl#L311-L328
>>
>> Once I played with s3curl the request with ordinary endpoint signing case
>> worked correctly.
>> Again, I'm not an expert of s3curl so no idea why your setting went to
>> the cname case tho.
>>
>> Best,
>> Kota
>>
>> (2018/06/01 14:49), Shyam Prasad N wrote:
>> > Hi Kota,
>> >
>> > Thanks for the response.
>> > When I specify the URL as http://s3server:8080/testbucket, it throws
>> back a
>> > SignatureDoesNotMatch error.
>> >
>> > eightkpc@objectstore1:~/s3curl$ ./s3curl.pl --debug --id=testerks
>> > --createBucket -- http://s3server:8080/testbucket
>> > s3curl: Found the url: host=s3server; port=8080; uri=/testbucket;
>> query=;
>> > s3curl: cname endpoint signing case
>> > s3curl: StringToSign='PUT\n\n\nFri, 01 Jun 2018 05:47:53
>> > +\n/s3server/testbucket'
>> > s3curl: exec curl -v -H 'Date: Fri, 01 Jun 2018 05:47:53 +' -H
>> > 'Authorization: AWS
>> > 76498e1413284b9d961d452db608dff4:uzQs5hJOnwY4dyFk0PIxHHwmVcA=' -L -H
>> > 'content-type: ' --data-binary  -X PUT http://s3server:8080/testbucket
>> > *   Trying 20.20.20.229...
>> > * TCP_NODELAY set
>> > * Connected to s3server (20.20.20.229) port 8080 (#0)
>> >> PUT /testbucket HTTP/1.1
>> >> Host: s3server:8080
>> >> User-Agent: curl/7.58.0
>> >> Accept: */*
>> >> Date: Fri, 01 Jun 2018 05:47:53 +
>> >> Authorization: AWS
>> > 76498e1413284b9d961d452db608dff4:uzQs5hJOnwY4dyFk0PIxHHwmVcA=
>> >> Content-Length: 0
>> >>
>> > < HTTP/1.1 403 Forbidden
>> > < x-amz-id-2: tx5c2ac9ea26a046ac96e4d-005b10de09
>> > < x-amz-request-id: tx5c2ac9ea26a046ac96e4d-005b10de09
>> > < Content-Type: application/xml
>> > < X-Trans-Id: tx5c2ac9ea26a046ac96e4d-005b10de09
>> > < X-Openstack-Request-Id: tx5c2ac9ea26a046ac96e4d-005b10de09
>> > < Date: Fri, 01 Jun 2018 05:47:53 GMT
>> > < Transfer-Encoding: chunked
>> > * HTTP error before end of send, stop sending
>> > <
>> > 
>> > * Closing connection 0
>> > SignatureDoesNotMatchThe request
>> signature we
>> > calculated does not match the signature you provided. Check your key and
>> > signing
>> > method.tx5c2ac9ea26a046ac96e4d-005b10de
>> 09
>> >
>> > Regards,
>> > Shyam
>> >
>> > On Fri, Jun 1, 2018 at 11:02 AM, Kota TSUYUZAKI <

Re: [Openstack] Struggling to get the s3 api interface to work with swift.

[Shyam Prasad N]

Hi Kota,

I tried with the changes you suggested. It gives me the old error again...
eightkpc@objectstore1:~/s3curl$ ./s3curl.pl --debug --id=testerks --
http://s3server:8080
s3curl: Found the url: host=s3server; port=8080; uri=; query=;
s3curl: s3server
s3curl: s3server
s3curl: ordinary endpoint signing case
s3curl: StringToSign='GET\n\n\nFri, 01 Jun 2018 11:31:50 +\n/'
s3curl: exec curl -v -H 'Date: Fri, 01 Jun 2018 11:31:50 +' -H
'Authorization: AWS
76498e1413284b9d961d452db608dff4:X1vdAhaZ4KyuM5LpMVc21ZQaGuA=' -L -H
'content-type: ' http://s3server:8080
* Rebuilt URL to: http://s3server:8080/
*   Trying 20.20.20.229...
* TCP_NODELAY set
* Connected to s3server (20.20.20.229) port 8080 (#0)
> GET / HTTP/1.1
> Host: s3server:8080
> User-Agent: curl/7.58.0
> Accept: */*
> Date: Fri, 01 Jun 2018 11:31:50 +
> Authorization: AWS
76498e1413284b9d961d452db608dff4:X1vdAhaZ4KyuM5LpMVc21ZQaGuA=
>
< HTTP/1.1 403 Forbidden
< x-amz-id-2: txbdd2940942ce49509226d-005b112ea6
< x-amz-request-id: txbdd2940942ce49509226d-005b112ea6
< Content-Type: application/xml
< X-Trans-Id: txbdd2940942ce49509226d-005b112ea6
< X-Openstack-Request-Id: txbdd2940942ce49509226d-005b112ea6
< Date: Fri, 01 Jun 2018 11:31:50 GMT
< Transfer-Encoding: chunked
<

* Connection #0 to host s3server left intact
SignatureDoesNotMatchThe request signature we
calculated does not match the signature you provided. Check your key and
signing
method.txbdd2940942ce49509226d-005b112ea6

On Fri, Jun 1, 2018 at 1:31 PM, Kota TSUYUZAKI  wrote:

> Hi Shyam,
>
>
> > s3curl: StringToSign='PUT\n\n\nFri, 01 Jun 2018 05:47:53
> > +\n/s3server/testbucket'
>
> It looks like your StringToSign doesn't include correct info for your
> request.(e.g. resource should be only "/testbucket")
> See https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-
> header-based-auth.html for more info.
>
> Your request should be:
>
> > * Connected to s3server (20.20.20.229) port 8080 (#0)
> >> PUT /testbucket HTTP/1.1
> >> Host: s3server:8080
> >> User-Agent: curl/7.58.0
> >> Accept: */*
> >> Date: Fri, 01 Jun 2018 05:47:53 +
> >> Authorization: AWS
> > 76498e1413284b9d961d452db608dff4:uzQs5hJOnwY4dyFk0PIxHHwmVcA=
> >> Content-Length: 0
>
> then, the string to sign should include the info corretly.
>
> Looking at s3curl code, it looks to fall into cname case?
>
> https://github.com/scality/S3/blob/master/tests/functional/
> s3curl/s3curl.pl#L311-L328
>
> Once I played with s3curl the request with ordinary endpoint signing case
> worked correctly.
> Again, I'm not an expert of s3curl so no idea why your setting went to the
> cname case tho.
>
> Best,
> Kota
>
> (2018/06/01 14:49), Shyam Prasad N wrote:
> > Hi Kota,
> >
> > Thanks for the response.
> > When I specify the URL as http://s3server:8080/testbucket, it throws
> back a
> > SignatureDoesNotMatch error.
> >
> > eightkpc@objectstore1:~/s3curl$ ./s3curl.pl --debug --id=testerks
> > --createBucket -- http://s3server:8080/testbucket
> > s3curl: Found the url: host=s3server; port=8080; uri=/testbucket; query=;
> > s3curl: cname endpoint signing case
> > s3curl: StringToSign='PUT\n\n\nFri, 01 Jun 2018 05:47:53
> > +\n/s3server/testbucket'
> > s3curl: exec curl -v -H 'Date: Fri, 01 Jun 2018 05:47:53 +' -H
> > 'Authorization: AWS
> > 76498e1413284b9d961d452db608dff4:uzQs5hJOnwY4dyFk0PIxHHwmVcA=' -L -H
> > 'content-type: ' --data-binary  -X PUT http://s3server:8080/testbucket
> > *   Trying 20.20.20.229...
> > * TCP_NODELAY set
> > * Connected to s3server (20.20.20.229) port 8080 (#0)
> >> PUT /testbucket HTTP/1.1
> >> Host: s3server:8080
> >> User-Agent: curl/7.58.0
> >> Accept: */*
> >> Date: Fri, 01 Jun 2018 05:47:53 +
> >> Authorization: AWS
> > 76498e1413284b9d961d452db608dff4:uzQs5hJOnwY4dyFk0PIxHHwmVcA=
> >> Content-Length: 0
> >>
> > < HTTP/1.1 403 Forbidden
> > < x-amz-id-2: tx5c2ac9ea26a046ac96e4d-005b10de09
> > < x-amz-request-id: tx5c2ac9ea26a046ac96e4d-005b10de09
> > < Content-Type: application/xml
> > < X-Trans-Id: tx5c2ac9ea26a046ac96e4d-005b10de09
> > < X-Openstack-Request-Id: tx5c2ac9ea26a046ac96e4d-005b10de09
> > < Date: Fri, 01 Jun 2018 05:47:53 GMT
> > < Transfer-Encoding: chunked
> > * HTTP error before end of send, stop sending
> > <
> > 
> > * Closing connection 0
> > SignatureDoesNotMatchThe request signature
> we
> > calculated does not match the signature you provided. Check your key and
> > signing
> > method.tx5c2ac9ea26a046ac96e4d-
> 005b10de09
> >
> > Regards,
> > Shyam
> >
> > On Fri, Jun 1, 2018 at 11:02 AM, Kota TSUYUZAKI <
> > tsuyuzaki.k...@lab.ntt.co.jp> wrote:
> >
> >> Hi Shyam,
> >>
> >> You should specify the path starts from bucket. It will be like
> >>
> >> http://20.20.20.229:8080/testBucket
> >>
> >> assuming you didn't configure virtual-hosted style.
> >> Even if your *Swift* endpoint is http://20.20.20.229:8080/v1/AUTH_
> >> dc86f7d8787b46158268bd77098b6578,
> >> swift3 doesn't require the account in the path so far as well as actual
> >> amazon s3.
> >>
> >> Best,

Re: [Openstack] Struggling to get the s3 api interface to work with swift.

[Yuxin Wang]

Hi Shyam,


It’s like what Kota said about StringToSign. And I think the point is that the 
host isn't equal to one of the endpoints 
listed(https://github.com/scality/S3/blob/master/tests/functional/s3curl/s3curl.pl#L32
 
),
 and it isn't the subdomain case too. So it goes to the cname case, where it’ll 
add an additional "/$host”.

You could try adding “s3server” to the endpoint list. Like:

```
my @endpoints = (
' 20.20.20.229',
'127.0.0.1’,
‘s3server'
);
```

Yuxin___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Struggling to get the s3 api interface to work with swift.

[Kota TSUYUZAKI]

Hi Shyam,


> s3curl: StringToSign='PUT\n\n\nFri, 01 Jun 2018 05:47:53
> +\n/s3server/testbucket'

It looks like your StringToSign doesn't include correct info for your 
request.(e.g. resource should be only "/testbucket")
See 
https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-header-based-auth.html 
for more info.

Your request should be:

> * Connected to s3server (20.20.20.229) port 8080 (#0)
>> PUT /testbucket HTTP/1.1
>> Host: s3server:8080
>> User-Agent: curl/7.58.0
>> Accept: */*
>> Date: Fri, 01 Jun 2018 05:47:53 +
>> Authorization: AWS
> 76498e1413284b9d961d452db608dff4:uzQs5hJOnwY4dyFk0PIxHHwmVcA=
>> Content-Length: 0

then, the string to sign should include the info corretly.

Looking at s3curl code, it looks to fall into cname case?

https://github.com/scality/S3/blob/master/tests/functional/s3curl/s3curl.pl#L311-L328

Once I played with s3curl the request with ordinary endpoint signing case 
worked correctly.
Again, I'm not an expert of s3curl so no idea why your setting went to the 
cname case tho.

Best,
Kota

(2018/06/01 14:49), Shyam Prasad N wrote:
> Hi Kota,
> 
> Thanks for the response.
> When I specify the URL as http://s3server:8080/testbucket, it throws back a
> SignatureDoesNotMatch error.
> 
> eightkpc@objectstore1:~/s3curl$ ./s3curl.pl --debug --id=testerks
> --createBucket -- http://s3server:8080/testbucket
> s3curl: Found the url: host=s3server; port=8080; uri=/testbucket; query=;
> s3curl: cname endpoint signing case
> s3curl: StringToSign='PUT\n\n\nFri, 01 Jun 2018 05:47:53
> +\n/s3server/testbucket'
> s3curl: exec curl -v -H 'Date: Fri, 01 Jun 2018 05:47:53 +' -H
> 'Authorization: AWS
> 76498e1413284b9d961d452db608dff4:uzQs5hJOnwY4dyFk0PIxHHwmVcA=' -L -H
> 'content-type: ' --data-binary  -X PUT http://s3server:8080/testbucket
> *   Trying 20.20.20.229...
> * TCP_NODELAY set
> * Connected to s3server (20.20.20.229) port 8080 (#0)
>> PUT /testbucket HTTP/1.1
>> Host: s3server:8080
>> User-Agent: curl/7.58.0
>> Accept: */*
>> Date: Fri, 01 Jun 2018 05:47:53 +
>> Authorization: AWS
> 76498e1413284b9d961d452db608dff4:uzQs5hJOnwY4dyFk0PIxHHwmVcA=
>> Content-Length: 0
>>
> < HTTP/1.1 403 Forbidden
> < x-amz-id-2: tx5c2ac9ea26a046ac96e4d-005b10de09
> < x-amz-request-id: tx5c2ac9ea26a046ac96e4d-005b10de09
> < Content-Type: application/xml
> < X-Trans-Id: tx5c2ac9ea26a046ac96e4d-005b10de09
> < X-Openstack-Request-Id: tx5c2ac9ea26a046ac96e4d-005b10de09
> < Date: Fri, 01 Jun 2018 05:47:53 GMT
> < Transfer-Encoding: chunked
> * HTTP error before end of send, stop sending
> <
> 
> * Closing connection 0
> SignatureDoesNotMatchThe request signature we
> calculated does not match the signature you provided. Check your key and
> signing
> method.tx5c2ac9ea26a046ac96e4d-005b10de09
> 
> Regards,
> Shyam
> 
> On Fri, Jun 1, 2018 at 11:02 AM, Kota TSUYUZAKI <
> tsuyuzaki.k...@lab.ntt.co.jp> wrote:
> 
>> Hi Shyam,
>>
>> You should specify the path starts from bucket. It will be like
>>
>> http://20.20.20.229:8080/testBucket
>>
>> assuming you didn't configure virtual-hosted style.
>> Even if your *Swift* endpoint is http://20.20.20.229:8080/v1/AUTH_
>> dc86f7d8787b46158268bd77098b6578,
>> swift3 doesn't require the account in the path so far as well as actual
>> amazon s3.
>>
>> Best,
>> Kota
>>
>> (2018/05/31 21:33), Shyam Prasad N wrote:
>>> Hi Yuxin,
>>>
>>> Thank you for sharing your configs.
>>> So I've managed to get past the Signature not matching error.
>>>
>>> Now the error is different. InvalidbucketName:
>>>
>>> eightkpc@objectstore1:~/s3curl$ ./s3curl.pl --debug --id=testerks
>>> --createBucket --
>>> http://20.20.20.229:8080/v1/AUTH_dc86f7d8787b46158268bd77098b65
>> 78/testBucket
>>> s3curl: Found the url: host=20.20.20.229; port=8080;
>>> uri=/v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket; query=;
>>> s3curl: cname endpoint signing case
>>> s3curl: StringToSign='PUT\n\n\nThu, 31 May 2018 12:02:57 +\n/
>>> 20.20.20.229/v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket'
>>> s3curl: exec curl -v -H 'Date: Thu, 31 May 2018 12:02:57 +' -H
>>> 'Authorization: AWS
>>> 76498e1413284b9d961d452db608dff4:jj/kaAEuX/vK+WUTvZyDQUUEGV0=' -L -H
>>> 'content-type: ' --data-binary  -X PUT
>>> http://20.20.20.229:8080/v1/AUTH_dc86f7d8787b46158268bd77098b65
>> 78/testBucket
>>> *   Trying 20.20.20.229...
>>> * TCP_NODELAY set
>>> * Connected to 20.20.20.229 (20.20.20.229) port 8080 (#0)
 PUT /v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket HTTP/1.1
 Host: 20.20.20.229:8080
 User-Agent: curl/7.58.0
 Accept: */*
 Date: Thu, 31 May 2018 12:02:57 +
 Authorization: AWS
>>> 76498e1413284b9d961d452db608dff4:jj/kaAEuX/vK+WUTvZyDQUUEGV0=
 Content-Length: 0

>>> < HTTP/1.1 400 Bad Request
>>> < x-amz-id-2: tx18266052d5044eb2a3bc7-005b0fe471
>>> < x-amz-request-id: tx18266052d5044eb2a3bc7-005b0fe471
>>> < Content-Type: application/xml
>>> < X-Trans-Id: tx18266052d5044eb2a3bc7-005b0fe471
>>> < X-Openstack-Request-Id: 

Re: [Openstack] Struggling to get the s3 api interface to work with swift.

[Shyam Prasad N]

Hi Kota,

Thanks for the response.
When I specify the URL as http://s3server:8080/testbucket, it throws back a
SignatureDoesNotMatch error.

eightkpc@objectstore1:~/s3curl$ ./s3curl.pl --debug --id=testerks
--createBucket -- http://s3server:8080/testbucket
s3curl: Found the url: host=s3server; port=8080; uri=/testbucket; query=;
s3curl: cname endpoint signing case
s3curl: StringToSign='PUT\n\n\nFri, 01 Jun 2018 05:47:53
+\n/s3server/testbucket'
s3curl: exec curl -v -H 'Date: Fri, 01 Jun 2018 05:47:53 +' -H
'Authorization: AWS
76498e1413284b9d961d452db608dff4:uzQs5hJOnwY4dyFk0PIxHHwmVcA=' -L -H
'content-type: ' --data-binary  -X PUT http://s3server:8080/testbucket
*   Trying 20.20.20.229...
* TCP_NODELAY set
* Connected to s3server (20.20.20.229) port 8080 (#0)
> PUT /testbucket HTTP/1.1
> Host: s3server:8080
> User-Agent: curl/7.58.0
> Accept: */*
> Date: Fri, 01 Jun 2018 05:47:53 +
> Authorization: AWS
76498e1413284b9d961d452db608dff4:uzQs5hJOnwY4dyFk0PIxHHwmVcA=
> Content-Length: 0
>
< HTTP/1.1 403 Forbidden
< x-amz-id-2: tx5c2ac9ea26a046ac96e4d-005b10de09
< x-amz-request-id: tx5c2ac9ea26a046ac96e4d-005b10de09
< Content-Type: application/xml
< X-Trans-Id: tx5c2ac9ea26a046ac96e4d-005b10de09
< X-Openstack-Request-Id: tx5c2ac9ea26a046ac96e4d-005b10de09
< Date: Fri, 01 Jun 2018 05:47:53 GMT
< Transfer-Encoding: chunked
* HTTP error before end of send, stop sending
<

* Closing connection 0
SignatureDoesNotMatchThe request signature we
calculated does not match the signature you provided. Check your key and
signing
method.tx5c2ac9ea26a046ac96e4d-005b10de09

Regards,
Shyam

On Fri, Jun 1, 2018 at 11:02 AM, Kota TSUYUZAKI <
tsuyuzaki.k...@lab.ntt.co.jp> wrote:

> Hi Shyam,
>
> You should specify the path starts from bucket. It will be like
>
> http://20.20.20.229:8080/testBucket
>
> assuming you didn't configure virtual-hosted style.
> Even if your *Swift* endpoint is http://20.20.20.229:8080/v1/AUTH_
> dc86f7d8787b46158268bd77098b6578,
> swift3 doesn't require the account in the path so far as well as actual
> amazon s3.
>
> Best,
> Kota
>
> (2018/05/31 21:33), Shyam Prasad N wrote:
> > Hi Yuxin,
> >
> > Thank you for sharing your configs.
> > So I've managed to get past the Signature not matching error.
> >
> > Now the error is different. InvalidbucketName:
> >
> > eightkpc@objectstore1:~/s3curl$ ./s3curl.pl --debug --id=testerks
> > --createBucket --
> > http://20.20.20.229:8080/v1/AUTH_dc86f7d8787b46158268bd77098b65
> 78/testBucket
> > s3curl: Found the url: host=20.20.20.229; port=8080;
> > uri=/v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket; query=;
> > s3curl: cname endpoint signing case
> > s3curl: StringToSign='PUT\n\n\nThu, 31 May 2018 12:02:57 +\n/
> > 20.20.20.229/v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket'
> > s3curl: exec curl -v -H 'Date: Thu, 31 May 2018 12:02:57 +' -H
> > 'Authorization: AWS
> > 76498e1413284b9d961d452db608dff4:jj/kaAEuX/vK+WUTvZyDQUUEGV0=' -L -H
> > 'content-type: ' --data-binary  -X PUT
> > http://20.20.20.229:8080/v1/AUTH_dc86f7d8787b46158268bd77098b65
> 78/testBucket
> > *   Trying 20.20.20.229...
> > * TCP_NODELAY set
> > * Connected to 20.20.20.229 (20.20.20.229) port 8080 (#0)
> >> PUT /v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket HTTP/1.1
> >> Host: 20.20.20.229:8080
> >> User-Agent: curl/7.58.0
> >> Accept: */*
> >> Date: Thu, 31 May 2018 12:02:57 +
> >> Authorization: AWS
> > 76498e1413284b9d961d452db608dff4:jj/kaAEuX/vK+WUTvZyDQUUEGV0=
> >> Content-Length: 0
> >>
> > < HTTP/1.1 400 Bad Request
> > < x-amz-id-2: tx18266052d5044eb2a3bc7-005b0fe471
> > < x-amz-request-id: tx18266052d5044eb2a3bc7-005b0fe471
> > < Content-Type: application/xml
> > < X-Trans-Id: tx18266052d5044eb2a3bc7-005b0fe471
> > < X-Openstack-Request-Id: tx18266052d5044eb2a3bc7-005b0fe471
> > < Date: Thu, 31 May 2018 12:02:57 GMT
> > < Transfer-Encoding: chunked
> > * HTTP error before end of send, stop sending
> > <
> > 
> > * Closing connection 0
> > InvalidBucketNameThe specified bucket is
> not
> > valid.tx18266052d5044eb2a3bc7-
> 005b0fe471v1 Error>eightkpc@objectstore1:~/s3curl$
> >
> >
> > My specified endpoint is
> > http://20.20.20.229:8080/v1/AUTH_dc86f7d8787b46158268bd77098b6578
> > What am I doing wrong?
> >
> > Regards,
> > Shyam
> >
> > On Wed, May 30, 2018 at 7:32 PM, Yuxin Wang 
> > wrote:
> >
> >> Hi Shyam,
> >>
> >> No problem. The output of the commands is attached.
> >>
> >> And my test cluster is on Swift v2.15.1 with Swift3 v1.12
> >>
> >> Also, here is the common process when I'm creating an S3 credential and
> >> using in s3curl. Hope it helps.
> >>
> >> 1. Create a user and a project, and assign a proper role.
> >>
> >> openstack project create testproject
> >> openstack user create testuser --password 123
> >> openstack role add --project testproject --user testuser _member_
> >>
> >> 2. Check accessibility to swift
> >>
> >> create a test-openrc file with above info
> >> source test-openrc
> >> swift list
> >>
> >> 3.Create a 

Re: [Openstack] Struggling to get the s3 api interface to work with swift.

[Kota TSUYUZAKI]

Hi Shyam,

You should specify the path starts from bucket. It will be like

http://20.20.20.229:8080/testBucket

assuming you didn't configure virtual-hosted style.
Even if your *Swift* endpoint is 
http://20.20.20.229:8080/v1/AUTH_dc86f7d8787b46158268bd77098b6578,
swift3 doesn't require the account in the path so far as well as actual amazon 
s3.

Best,
Kota

(2018/05/31 21:33), Shyam Prasad N wrote:
> Hi Yuxin,
> 
> Thank you for sharing your configs.
> So I've managed to get past the Signature not matching error.
> 
> Now the error is different. InvalidbucketName:
> 
> eightkpc@objectstore1:~/s3curl$ ./s3curl.pl --debug --id=testerks
> --createBucket --
> http://20.20.20.229:8080/v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket
> s3curl: Found the url: host=20.20.20.229; port=8080;
> uri=/v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket; query=;
> s3curl: cname endpoint signing case
> s3curl: StringToSign='PUT\n\n\nThu, 31 May 2018 12:02:57 +\n/
> 20.20.20.229/v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket'
> s3curl: exec curl -v -H 'Date: Thu, 31 May 2018 12:02:57 +' -H
> 'Authorization: AWS
> 76498e1413284b9d961d452db608dff4:jj/kaAEuX/vK+WUTvZyDQUUEGV0=' -L -H
> 'content-type: ' --data-binary  -X PUT
> http://20.20.20.229:8080/v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket
> *   Trying 20.20.20.229...
> * TCP_NODELAY set
> * Connected to 20.20.20.229 (20.20.20.229) port 8080 (#0)
>> PUT /v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket HTTP/1.1
>> Host: 20.20.20.229:8080
>> User-Agent: curl/7.58.0
>> Accept: */*
>> Date: Thu, 31 May 2018 12:02:57 +
>> Authorization: AWS
> 76498e1413284b9d961d452db608dff4:jj/kaAEuX/vK+WUTvZyDQUUEGV0=
>> Content-Length: 0
>>
> < HTTP/1.1 400 Bad Request
> < x-amz-id-2: tx18266052d5044eb2a3bc7-005b0fe471
> < x-amz-request-id: tx18266052d5044eb2a3bc7-005b0fe471
> < Content-Type: application/xml
> < X-Trans-Id: tx18266052d5044eb2a3bc7-005b0fe471
> < X-Openstack-Request-Id: tx18266052d5044eb2a3bc7-005b0fe471
> < Date: Thu, 31 May 2018 12:02:57 GMT
> < Transfer-Encoding: chunked
> * HTTP error before end of send, stop sending
> <
> 
> * Closing connection 0
> InvalidBucketNameThe specified bucket is not
> valid.tx18266052d5044eb2a3bc7-005b0fe471v1eightkpc@objectstore1:~/s3curl$
> 
> 
> My specified endpoint is
> http://20.20.20.229:8080/v1/AUTH_dc86f7d8787b46158268bd77098b6578
> What am I doing wrong?
> 
> Regards,
> Shyam
> 
> On Wed, May 30, 2018 at 7:32 PM, Yuxin Wang 
> wrote:
> 
>> Hi Shyam,
>>
>> No problem. The output of the commands is attached.
>>
>> And my test cluster is on Swift v2.15.1 with Swift3 v1.12
>>
>> Also, here is the common process when I'm creating an S3 credential and
>> using in s3curl. Hope it helps.
>>
>> 1. Create a user and a project, and assign a proper role.
>>
>> openstack project create testproject
>> openstack user create testuser --password 123
>> openstack role add --project testproject --user testuser _member_
>>
>> 2. Check accessibility to swift
>>
>> create a test-openrc file with above info
>> source test-openrc
>> swift list
>>
>> 3.Create a credential
>>
>> openstack credential create --type ec2 --project testproject testuser
>>  '{"access": "testaccess", "secret": "testsecret"}'
>>
>> 4. Use it in s3curl
>>
>> add the endpoint url to `my @endpoints` in s3curl.pl
>> add the credential to .s3curl config file
>>
>> do `s3curl.pl -i cred_name --debug -- http://endpoint -X GET`
>>
>>
>>
>>
>> 在 2018年5月25日，18:17，Shyam Prasad N  写道：
>>
>> Hi Yuxin,
>>
>> If you don't mind, can you share the output of the following commands in
>> your running swift3 setup?
>>
>> openstack credential list
>> openstack ec2 credentials list
>> cat /etc/swift/proxy-server.conf
>>
>> Also, what are the access keys and secret keys that you use?
>> I want to make sure that I'm not missing anything in configuration.
>>
>> Regards,
>> Shyam
>>
>> On Fri, May 25, 2018 at 3:05 PM, Shyam Prasad N 
>> wrote:
>>
>>> Tried that. Unfortunately same error.
>>> Is there anything I can do to troubleshoot this?
>>>
>>> On Fri, May 25, 2018 at 2:56 PM, Yuxin Wang 
>>> wrote:
>>>
 They can be any strings.

 Replace them with whatever you want.

 - Yuxin

 在 2018年5月25日，14:57，Shyam Prasad N  写道：

 Thanks. I'll try this.
 But what values do I use in place of ak and sk? I want to use some
 command to get those values, right?

 On Fri, May 25, 2018 at 9:52 AM, Yuxin Wang 
  wrote:

> I created ec2 credentials using command `openstack credential create`.
>
> i.e.
>
> openstack credential create --type ec2 --project proj user '{"access":
> "ak", "secret": "sk”}'
>
>
> It seems the two credentials are not the same thing.
>
> Ref:
>
> https://www.ibm.com/support/knowledgecenter/en/STXKQY_4.1.1/
> com.ibm.spectrum.scale.v4r11.adv.doc/bl1adv_ConfigureOpensta
> ckEC2credentials.htm
> 

Re: [Openstack] Struggling to get the s3 api interface to work with swift.

[Shyam Prasad N]

Hi Yuxin,

Thank you for sharing your configs.
So I've managed to get past the Signature not matching error.

Now the error is different. InvalidbucketName:

eightkpc@objectstore1:~/s3curl$ ./s3curl.pl --debug --id=testerks
--createBucket --
http://20.20.20.229:8080/v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket
s3curl: Found the url: host=20.20.20.229; port=8080;
uri=/v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket; query=;
s3curl: cname endpoint signing case
s3curl: StringToSign='PUT\n\n\nThu, 31 May 2018 12:02:57 +\n/
20.20.20.229/v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket'
s3curl: exec curl -v -H 'Date: Thu, 31 May 2018 12:02:57 +' -H
'Authorization: AWS
76498e1413284b9d961d452db608dff4:jj/kaAEuX/vK+WUTvZyDQUUEGV0=' -L -H
'content-type: ' --data-binary  -X PUT
http://20.20.20.229:8080/v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket
*   Trying 20.20.20.229...
* TCP_NODELAY set
* Connected to 20.20.20.229 (20.20.20.229) port 8080 (#0)
> PUT /v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket HTTP/1.1
> Host: 20.20.20.229:8080
> User-Agent: curl/7.58.0
> Accept: */*
> Date: Thu, 31 May 2018 12:02:57 +
> Authorization: AWS
76498e1413284b9d961d452db608dff4:jj/kaAEuX/vK+WUTvZyDQUUEGV0=
> Content-Length: 0
>
< HTTP/1.1 400 Bad Request
< x-amz-id-2: tx18266052d5044eb2a3bc7-005b0fe471
< x-amz-request-id: tx18266052d5044eb2a3bc7-005b0fe471
< Content-Type: application/xml
< X-Trans-Id: tx18266052d5044eb2a3bc7-005b0fe471
< X-Openstack-Request-Id: tx18266052d5044eb2a3bc7-005b0fe471
< Date: Thu, 31 May 2018 12:02:57 GMT
< Transfer-Encoding: chunked
* HTTP error before end of send, stop sending
<

* Closing connection 0
InvalidBucketNameThe specified bucket is not
valid.tx18266052d5044eb2a3bc7-005b0fe471v1eightkpc@objectstore1:~/s3curl$


My specified endpoint is
http://20.20.20.229:8080/v1/AUTH_dc86f7d8787b46158268bd77098b6578
What am I doing wrong?

Regards,
Shyam

On Wed, May 30, 2018 at 7:32 PM, Yuxin Wang 
wrote:

> Hi Shyam,
>
> No problem. The output of the commands is attached.
>
> And my test cluster is on Swift v2.15.1 with Swift3 v1.12
>
> Also, here is the common process when I'm creating an S3 credential and
> using in s3curl. Hope it helps.
>
> 1. Create a user and a project, and assign a proper role.
>
> openstack project create testproject
> openstack user create testuser --password 123
> openstack role add --project testproject --user testuser _member_
>
> 2. Check accessibility to swift
>
> create a test-openrc file with above info
> source test-openrc
> swift list
>
> 3.Create a credential
>
> openstack credential create --type ec2 --project testproject testuser
>  '{"access": "testaccess", "secret": "testsecret"}'
>
> 4. Use it in s3curl
>
> add the endpoint url to `my @endpoints` in s3curl.pl
> add the credential to .s3curl config file
>
> do `s3curl.pl -i cred_name --debug -- http://endpoint -X GET`
>
>
>
>
> 在 2018年5月25日，18:17，Shyam Prasad N  写道：
>
> Hi Yuxin,
>
> If you don't mind, can you share the output of the following commands in
> your running swift3 setup?
>
> openstack credential list
> openstack ec2 credentials list
> cat /etc/swift/proxy-server.conf
>
> Also, what are the access keys and secret keys that you use?
> I want to make sure that I'm not missing anything in configuration.
>
> Regards,
> Shyam
>
> On Fri, May 25, 2018 at 3:05 PM, Shyam Prasad N 
> wrote:
>
>> Tried that. Unfortunately same error.
>> Is there anything I can do to troubleshoot this?
>>
>> On Fri, May 25, 2018 at 2:56 PM, Yuxin Wang 
>> wrote:
>>
>>> They can be any strings.
>>>
>>> Replace them with whatever you want.
>>>
>>> - Yuxin
>>>
>>> 在 2018年5月25日，14:57，Shyam Prasad N  写道：
>>>
>>> Thanks. I'll try this.
>>> But what values do I use in place of ak and sk? I want to use some
>>> command to get those values, right?
>>>
>>> On Fri, May 25, 2018 at 9:52 AM, Yuxin Wang 
>>>  wrote:
>>>
 I created ec2 credentials using command `openstack credential create`.

 i.e.

 openstack credential create --type ec2 --project proj user '{"access":
 "ak", "secret": "sk”}'


 It seems the two credentials are not the same thing.

 Ref:

 https://www.ibm.com/support/knowledgecenter/en/STXKQY_4.1.1/
 com.ibm.spectrum.scale.v4r11.adv.doc/bl1adv_ConfigureOpensta
 ckEC2credentials.htm
 

 在 2018年5月25日，10:32，Shyam Prasad N  写道：

 Yes, I did.
 I don't think this is s3curl related issue, because I tried with python
 AWS SDK, and got the same error.

 On Fri, May 25, 2018, 07:42 Yuxin Wang 
 wrote:

> Did you add 127.0.0.1 

Re: [Openstack] Struggling to get the s3 api interface to work with swift.

[Yuxin Wang]

Hi Shyam,No problem. The output of the commands is attached.And my test cluster is on Swift v2.15.1 with Swift3 v1.12Also, here is the common process when I'm creating an S3 credential and using in s3curl. Hope it helps.1. Create a user and a project, and assign a proper role.openstack project create testprojectopenstack user create testuser --password 123openstack role add --project testproject --user testuser _member_2. Check accessibility to swiftcreate a test-openrc file with above infosource test-openrcswift list3.Create a credentialopenstack credential create --type ec2 --project testproject testuser  '{"access": "testaccess", "secret": "testsecret"}'4. Use it in s3curladd the endpoint url to `my @endpoints` in s3curl.pladd the credential to .s3curl config filedo `s3curl.pl -i cred_name --debug -- http://endpoint -X GET`[root@yuxin ~]# source admin_openrc
[root@yuxin ~]# openstack credential list
+--+--+--+--+--+
| ID   | Type | 
User ID  | Data 
| Project ID   |
+--+--+--+--+--+
| 46ed9bf036c0235deb16d6043a07e4c41712d5b7c1509fe62acbbcbfd7fb6a27 | ec2  | 
f925686c23164b159fa8e50fea56a779 | {"access": "testalt", "secret": 
"testsecret"} | 9fa44d783eda4716a3553dcff577658b |
| 6410886953a4c46ed9bf036c0235deb0ee42df222fd21b1e79bad1e0ff7b027e | ec2  | 
56a77946146c4297a73ccfe7c51dba2b | {"access": "wyxak", "secret": "wyxsk"}   
| 5646628e280043b9a6a1c3dd5dcbb48e |
+--+--+--+--+--+
[root@yuxin ~]# openstack ec2 credentials list

[root@yuxin ~]# swift info
Core: swift
 Options:
  account_autocreate: True
  account_listing_limit: 1
  allow_account_management: True
  container_listing_limit: 1
  extra_header_count: 0
  max_account_name_length: 256
  max_container_name_length: 256
  max_file_size: 5368709122
  max_header_size: 8192
  max_meta_count: 90
  max_meta_name_length: 128
  max_meta_overall_size: 4096
  max_meta_value_length: 256
  max_object_name_length: 1024
  policies: [{u'name': u'Policy-0', u'aliases': u'Policy-0, yellow, orange'}, 
{u'name': u'region-1', u'aliases': u'region-1'}, {u'name': u'component1-01', 
u'aliases': u'component1-01'}, {u'name': u'component1-02', u'aliases': 
u'component1-02'}, {u'name': u'composite1', u'aliases': u'composite1'}, 
{u'name': u'ec-component1', u'aliases': u'ec-component1'}, {u'name': 
u'ec-component2', u'aliases': u'ec-component2'}, {u'name': u'ec-composite', 
u'aliases': u'ec-composite'}, {u'name': u'replica-component2-1', u'aliases': 
u'replica-component2-1'}, {u'name': u'replica-component2-2', u'aliases': 
u'replica-component2-2'}, {u'name': u'replica-composite2', u'aliases': 
u'replica-composite2'}, {u'name': u'replica-2-11', u'aliases': 
u'replica-2-11'}, {u'name': u'replica-2-12', u'aliases': u'replica-2-12'}, 
{u'name': u'replica-2x2-13', u'aliases': u'replica-2x2-13'}, {u'name': 
u'ec42x2', u'aliases': u'ec42x2'}, {u'name': u'ppt', u'aliases': u'ppt, ec'}, 
{u'name': u'test992', u'aliases': u'test992'}, {u'default': True, u'name': 
u'105-local', u'aliases': u'105-local'}, {u'name': u'replica36', u'aliases': 
u'replica36'}, {u'name': u'replica38', u'aliases': u'replica38'}, {u'name': 
u'replica37', u'aliases': u'replica37'}]
  strict_cors_mode: True
  version: 2.15.1
Additional middleware: account_quotas
Additional middleware: bulk_delete
 Options:
  max_deletes_per_request: 1
  max_failed_deletes: 1000
Additional middleware: bulk_upload
 Options:
  max_containers_per_extraction: 1
  max_failed_extractions: 1000
Additional middleware: container_quotas
Additional middleware: container_sync
 Options:
  realms: {}
Additional middleware: formpost
Additional middleware: ratelimit
 Options:
  account_ratelimit: 0.0
  container_listing_ratelimits: []
  container_ratelimits: []
  max_sleep_time_seconds: 60.0
Additional middleware: slo
 Options:
  max_manifest_segments: 1000
  max_manifest_size: 2097152
  min_segment_size: 1
Additional middleware: swift3
 Options:
  allow_multipart_uploads: True
  max_bucket_listing: 1000
  max_multi_delete_objects: 1000
  max_parts_listing: 1000
  max_upload_part_num: 1000
  version: 1.12.0
Additional middleware: tempurl
 Options:
  incoming_allow_headers: []
  incoming_remove_headers: [u'x-timestamp']
  methods: [u'GET', u'HEAD', u'PUT', u'POST', u'DELETE']
  outgoing_allow_headers: 

Re: [Openstack] Struggling to get the s3 api interface to work with swift.

[Shyam Prasad N]

Hi Yuxin,

If you don't mind, can you share the output of the following commands in
your running swift3 setup?

openstack credential list
openstack ec2 credentials list
cat /etc/swift/proxy-server.conf

Also, what are the access keys and secret keys that you use?
I want to make sure that I'm not missing anything in configuration.

Regards,
Shyam

On Fri, May 25, 2018 at 3:05 PM, Shyam Prasad N 
wrote:

> Tried that. Unfortunately same error.
> Is there anything I can do to troubleshoot this?
>
> On Fri, May 25, 2018 at 2:56 PM, Yuxin Wang 
> wrote:
>
>> They can be any strings.
>>
>> Replace them with whatever you want.
>>
>> - Yuxin
>>
>> 在 2018年5月25日，14:57，Shyam Prasad N  写道：
>>
>> Thanks. I'll try this.
>> But what values do I use in place of ak and sk? I want to use some
>> command to get those values, right?
>>
>> On Fri, May 25, 2018 at 9:52 AM, Yuxin Wang 
>> wrote:
>>
>>> I created ec2 credentials using command `openstack credential create`.
>>>
>>> i.e.
>>>
>>> openstack credential create --type ec2 --project proj user '{"access":
>>> "ak", "secret": "sk”}'
>>>
>>>
>>> It seems the two credentials are not the same thing.
>>>
>>> Ref:
>>>
>>> https://www.ibm.com/support/knowledgecenter/en/STXKQY_4.1.1/
>>> com.ibm.spectrum.scale.v4r11.adv.doc/bl1adv_ConfigureOpensta
>>> ckEC2credentials.htm
>>> 
>>>
>>> 在 2018年5月25日，10:32，Shyam Prasad N  写道：
>>>
>>> Yes, I did.
>>> I don't think this is s3curl related issue, because I tried with python
>>> AWS SDK, and got the same error.
>>>
>>> On Fri, May 25, 2018, 07:42 Yuxin Wang 
>>> wrote:
>>>
 Did you add 127.0.0.1 to the endpoint list in s3curl.pl
 
 ?

 i.e.

 my @endpoints = (‘127.0.0.1’);

 在 2018年5月24日，19:48，Shyam Prasad N  写道：

 Hi,

 I've been trying to get swift3 to work for several days now. But I
 haven't managed to get it running.
 Both with tempauth and keystoneauth, I'm getting the same error:

 eightkpc@objectstore1:~/s3curl$ ./s3curl.pl
 
 --id=testerks -- http://127.0.0.1:8080/
 
 
 SignatureDoesNotMatchThe request
 signature we calculated does not match the signature you provided. Check
 your key and signing method.tx
 a691e7ca97a44d56bc4c2-005b06a292

 May 24 11:31:30 localhost proxy-server: 127.0.0.1 127.0.0.1
 24/May/2018/11/31/30 GET / HTTP/1.0 403 - curl/7.58.0 - - 277 -
 txa691e7ca97a44d56bc4c2-005b06a292 - 0.0200 - - 1527161490.543112040
 1527161490.563107014 -
 May 24 11:31:30 localhost proxy-server: STDERR: 127.0.0.1 - -
 [24/May/2018 11:31:30] "GET / HTTP/1.1" 403 621 0.021979 (txn:
 txa691e7ca97a44d56bc4c2-005b06a292)

 eightkpc@objectstore1:~$ cat .s3curl
 %awsSecretAccessKeys = (
 tester => {
 id => 'test:tester',
 key => 'testing',
 },
 testerks => {
 id => 'e6289a1b5692461388d0597a4873d054',
 key => '88bb706887094696b082f008ba133ad7',
 },
 );

 eightkpc@objectstore1:~$ openstack ec2 credentials show
 e6289a1b5692461388d0597a4873d054
 ++--
 
 --+
 | Field  | Value

  |
 ++--
 
 --+
 | access | e6289a1b5692461388d0597a4873d0
 54
  |
 | links  | {u'self': u'http://controller:5000/v3/us
 

Re: [Openstack] Struggling to get the s3 api interface to work with swift.

[Shyam Prasad N]

Tried that. Unfortunately same error.
Is there anything I can do to troubleshoot this?

On Fri, May 25, 2018 at 2:56 PM, Yuxin Wang 
wrote:

> They can be any strings.
>
> Replace them with whatever you want.
>
> - Yuxin
>
> 在 2018年5月25日，14:57，Shyam Prasad N  写道：
>
> Thanks. I'll try this.
> But what values do I use in place of ak and sk? I want to use some command
> to get those values, right?
>
> On Fri, May 25, 2018 at 9:52 AM, Yuxin Wang 
> wrote:
>
>> I created ec2 credentials using command `openstack credential create`.
>>
>> i.e.
>>
>> openstack credential create --type ec2 --project proj user '{"access":
>> "ak", "secret": "sk”}'
>>
>>
>> It seems the two credentials are not the same thing.
>>
>> Ref:
>>
>> https://www.ibm.com/support/knowledgecenter/en/STXKQY_4.1.1/
>> com.ibm.spectrum.scale.v4r11.adv.doc/bl1adv_ConfigureOpenst
>> ackEC2credentials.htm
>> 
>>
>> 在 2018年5月25日，10:32，Shyam Prasad N  写道：
>>
>> Yes, I did.
>> I don't think this is s3curl related issue, because I tried with python
>> AWS SDK, and got the same error.
>>
>> On Fri, May 25, 2018, 07:42 Yuxin Wang 
>> wrote:
>>
>>> Did you add 127.0.0.1 to the endpoint list in s3curl.pl
>>> 
>>> ?
>>>
>>> i.e.
>>>
>>> my @endpoints = (‘127.0.0.1’);
>>>
>>> 在 2018年5月24日，19:48，Shyam Prasad N  写道：
>>>
>>> Hi,
>>>
>>> I've been trying to get swift3 to work for several days now. But I
>>> haven't managed to get it running.
>>> Both with tempauth and keystoneauth, I'm getting the same error:
>>>
>>> eightkpc@objectstore1:~/s3curl$ ./s3curl.pl
>>> 
>>> --id=testerks -- http://127.0.0.1:8080/
>>> 
>>> 
>>> SignatureDoesNotMatchThe request signature
>>> we calculated does not match the signature you provided. Check your key and
>>> signing method.txa691e7ca97a44d56bc4c2-005b06a2
>>> 92
>>>
>>> May 24 11:31:30 localhost proxy-server: 127.0.0.1 127.0.0.1
>>> 24/May/2018/11/31/30 GET / HTTP/1.0 403 - curl/7.58.0 - - 277 -
>>> txa691e7ca97a44d56bc4c2-005b06a292 - 0.0200 - - 1527161490.543112040
>>> 1527161490.563107014 -
>>> May 24 11:31:30 localhost proxy-server: STDERR: 127.0.0.1 - -
>>> [24/May/2018 11:31:30] "GET / HTTP/1.1" 403 621 0.021979 (txn:
>>> txa691e7ca97a44d56bc4c2-005b06a292)
>>>
>>> eightkpc@objectstore1:~$ cat .s3curl
>>> %awsSecretAccessKeys = (
>>> tester => {
>>> id => 'test:tester',
>>> key => 'testing',
>>> },
>>> testerks => {
>>> id => 'e6289a1b5692461388d0597a4873d054',
>>> key => '88bb706887094696b082f008ba133ad7',
>>> },
>>> );
>>>
>>> eightkpc@objectstore1:~$ openstack ec2 credentials show
>>> e6289a1b5692461388d0597a4873d054
>>> ++--
>>> 
>>> --+
>>> | Field  | Value
>>>
>>>  |
>>> ++--
>>> 
>>> --+
>>> | access | e6289a1b5692461388d0597a4873d0
>>> 54
>>>  |
>>> | links  | {u'self': u'http://controller:5000/v3/us
>>> ers/d7df7b56343b4ea988869fc30efeda09/credentials/OS-EC2/e628
>>> 9a1b5692461388d0597a4873d054'} |
>>> | project_id | dc86f7d8787b46158268bd77098b65
>>> 78
>>>  |
>>> | secret | 88bb706887094696b082f008ba133a
>>> d7
>>>  |
>>> | trust_id   | None
>>>
>>>  |
>>> | user_id| d7df7b56343b4ea988869fc30efeda
>>> 09
>>>  |
>>> ++--
>>> 

Re: [Openstack] Struggling to get the s3 api interface to work with swift.

[Shyam Prasad N]

I'm using Queens on Ubuntu 18.04.

On Fri, May 25, 2018 at 1:54 PM, John van Ommen 
wrote:

> What release are you using?
>
> In 2016 I tried to get this working for a client of mine at HPE, and found
> that it wouldn't work without a fair bit of hacking. Basically the software
> hadn't been updated in about a year, and the newest release was
> incompatible with the version of OpenStack that we were selling.
>
> On Thu, May 24, 2018 at 11:57 PM, Shyam Prasad N 
> wrote:
>
>> Thanks. I'll try this.
>> But what values do I use in place of ak and sk? I want to use some
>> command to get those values, right?
>>
>> On Fri, May 25, 2018 at 9:52 AM, Yuxin Wang 
>> wrote:
>>
>>> I created ec2 credentials using command `openstack credential create`.
>>>
>>> i.e.
>>>
>>> openstack credential create --type ec2 --project proj user '{"access":
>>> "ak", "secret": "sk”}'
>>>
>>>
>>> It seems the two credentials are not the same thing.
>>>
>>> Ref:
>>>
>>> https://www.ibm.com/support/knowledgecenter/en/STXKQY_4.1.1/
>>> com.ibm.spectrum.scale.v4r11.adv.doc/bl1adv_ConfigureOpensta
>>> ckEC2credentials.htm
>>>
>>> 在 2018年5月25日，10:32，Shyam Prasad N  写道：
>>>
>>> Yes, I did.
>>> I don't think this is s3curl related issue, because I tried with python
>>> AWS SDK, and got the same error.
>>>
>>> On Fri, May 25, 2018, 07:42 Yuxin Wang 
>>> wrote:
>>>
 Did you add 127.0.0.1 to the endpoint list in s3curl.pl?

 i.e.

 my @endpoints = (‘127.0.0.1’);

 在 2018年5月24日，19:48，Shyam Prasad N  写道：

 Hi,

 I've been trying to get swift3 to work for several days now. But I
 haven't managed to get it running.
 Both with tempauth and keystoneauth, I'm getting the same error:

 eightkpc@objectstore1:~/s3curl$ ./s3curl.pl
 
 --id=testerks -- http://127.0.0.1:8080/
 
 
 SignatureDoesNotMatchThe request
 signature we calculated does not match the signature you provided. Check
 your key and signing method.tx
 a691e7ca97a44d56bc4c2-005b06a292

 May 24 11:31:30 localhost proxy-server: 127.0.0.1 127.0.0.1
 24/May/2018/11/31/30 GET / HTTP/1.0 403 - curl/7.58.0 - - 277 -
 txa691e7ca97a44d56bc4c2-005b06a292 - 0.0200 - - 1527161490.543112040
 1527161490.563107014 -
 May 24 11:31:30 localhost proxy-server: STDERR: 127.0.0.1 - -
 [24/May/2018 11:31:30] "GET / HTTP/1.1" 403 621 0.021979 (txn:
 txa691e7ca97a44d56bc4c2-005b06a292)

 eightkpc@objectstore1:~$ cat .s3curl
 %awsSecretAccessKeys = (
 tester => {
 id => 'test:tester',
 key => 'testing',
 },
 testerks => {
 id => 'e6289a1b5692461388d0597a4873d054',
 key => '88bb706887094696b082f008ba133ad7',
 },
 );

 eightkpc@objectstore1:~$ openstack ec2 credentials show
 e6289a1b5692461388d0597a4873d054
 ++--
 
 --+
 | Field  | Value

  |
 ++--
 
 --+
 | access | e6289a1b5692461388d0597a4873d0
 54
  |
 | links  | {u'self': u'http://controller:5000/v3/us
 ers/d7df7b56343b4ea988869fc30efeda09/credentials/OS-EC2/e628
 9a1b5692461388d0597a4873d054'} |
 | project_id | dc86f7d8787b46158268bd77098b65
 78
  |
 | secret | 88bb706887094696b082f008ba133a
 d7
  |
 | trust_id   | None

  |
 | user_id| d7df7b56343b4ea988869fc30efeda
 09
  |
 ++--
 
 --+

 Can someone please let me know what is going on?

 Regards,
 Shyam
 ___
 Mailing list: https://eur03.safelinks.protec
 

Re: [Openstack] Struggling to get the s3 api interface to work with swift.

[Yuxin Wang]

They can be any strings.

Replace them with whatever you want.

- Yuxin

> 在 2018年5月25日，14:57，Shyam Prasad N  写道：
> 
> Thanks. I'll try this. 
> But what values do I use in place of ak and sk? I want to use some command to 
> get those values, right?
> 
> On Fri, May 25, 2018 at 9:52 AM, Yuxin Wang  > wrote:
> I created ec2 credentials using command `openstack credential create`.
> 
> i.e.
> 
> openstack credential create --type ec2 --project proj user '{"access": "ak", 
> "secret": "sk”}'
> 
> 
> It seems the two credentials are not the same thing.
> 
> Ref:
> 
> https://www.ibm.com/support/knowledgecenter/en/STXKQY_4.1.1/com.ibm.spectrum.scale.v4r11.adv.doc/bl1adv_ConfigureOpenstackEC2credentials.htm
>  
> 
> 
>> 在 2018年5月25日，10:32，Shyam Prasad N > > 写道：
>> 
>> Yes, I did.
>> I don't think this is s3curl related issue, because I tried with python AWS 
>> SDK, and got the same error. 
>> 
>> On Fri, May 25, 2018, 07:42 Yuxin Wang > > wrote:
>> Did you add 127.0.0.1 to the endpoint list in s3curl.pl 
>> ?
>> 
>> i.e.
>> 
>> my @endpoints = (‘127.0.0.1’);
>> 
>>> 在 2018年5月24日，19:48，Shyam Prasad N >> > 写道：
>>> 
>>> Hi,
>>> 
>>> I've been trying to get swift3 to work for several days now. But I haven't 
>>> managed to get it running. 
>>> Both with tempauth and keystoneauth, I'm getting the same error:
>>> 
>>> eightkpc@objectstore1:~/s3curl$ ./s3curl.pl 
>>> 
>>>  --id=testerks -- http://127.0.0.1:8080/ 
>>> 
>>> 
>>> SignatureDoesNotMatchThe request signature we 
>>> calculated does not match the signature you provided. Check your key and 
>>> signing 
>>> method.txa691e7ca97a44d56bc4c2-005b06a292
>>> 
>>> May 24 11:31:30 localhost proxy-server: 127.0.0.1 127.0.0.1 
>>> 24/May/2018/11/31/30 GET / HTTP/1.0 403 - curl/7.58.0 - - 277 - 
>>> txa691e7ca97a44d56bc4c2-005b06a292 - 0.0200 - - 1527161490.543112040 
>>> 1527161490.563107014 -
>>> May 24 11:31:30 localhost proxy-server: STDERR: 127.0.0.1 - - [24/May/2018 
>>> 11:31:30] "GET / HTTP/1.1" 403 621 0.021979 (txn: 
>>> txa691e7ca97a44d56bc4c2-005b06a292)
>>> 
>>> eightkpc@objectstore1:~$ cat .s3curl 
>>> %awsSecretAccessKeys = (
>>> tester => {
>>> id => 'test:tester',
>>> key => 'testing',
>>> },
>>> testerks => {
>>> id => 'e6289a1b5692461388d0597a4873d054',
>>> key => '88bb706887094696b082f008ba133ad7',
>>> },
>>> );
>>> 
>>> eightkpc@objectstore1:~$ openstack ec2 credentials show 
>>> e6289a1b5692461388d0597a4873d054
>>> +++
>>> | Field  | Value
>>>   |
>>> +++
>>> | access | e6289a1b5692461388d0597a4873d054 
>>>   |
>>> | links  | {u'self': 
>>> u'http://controller:5000/v3/users/d7df7b56343b4ea988869fc30efeda09/credentials/OS-EC2/e6289a1b5692461388d0597a4873d054
>>>  
>>> '}
>>>  |
>>> | project_id | dc86f7d8787b46158268bd77098b6578 
>>>   |
>>> | secret | 88bb706887094696b082f008ba133ad7 
>>>   

Re: [Openstack] Struggling to get the s3 api interface to work with swift.

[John van Ommen]

What release are you using?

In 2016 I tried to get this working for a client of mine at HPE, and found
that it wouldn't work without a fair bit of hacking. Basically the software
hadn't been updated in about a year, and the newest release was
incompatible with the version of OpenStack that we were selling.

On Thu, May 24, 2018 at 11:57 PM, Shyam Prasad N 
wrote:

> Thanks. I'll try this.
> But what values do I use in place of ak and sk? I want to use some command
> to get those values, right?
>
> On Fri, May 25, 2018 at 9:52 AM, Yuxin Wang 
> wrote:
>
>> I created ec2 credentials using command `openstack credential create`.
>>
>> i.e.
>>
>> openstack credential create --type ec2 --project proj user '{"access":
>> "ak", "secret": "sk”}'
>>
>>
>> It seems the two credentials are not the same thing.
>>
>> Ref:
>>
>> https://www.ibm.com/support/knowledgecenter/en/STXKQY_4.1.1/
>> com.ibm.spectrum.scale.v4r11.adv.doc/bl1adv_ConfigureOpenst
>> ackEC2credentials.htm
>>
>> 在 2018年5月25日，10:32，Shyam Prasad N  写道：
>>
>> Yes, I did.
>> I don't think this is s3curl related issue, because I tried with python
>> AWS SDK, and got the same error.
>>
>> On Fri, May 25, 2018, 07:42 Yuxin Wang 
>> wrote:
>>
>>> Did you add 127.0.0.1 to the endpoint list in s3curl.pl?
>>>
>>> i.e.
>>>
>>> my @endpoints = (‘127.0.0.1’);
>>>
>>> 在 2018年5月24日，19:48，Shyam Prasad N  写道：
>>>
>>> Hi,
>>>
>>> I've been trying to get swift3 to work for several days now. But I
>>> haven't managed to get it running.
>>> Both with tempauth and keystoneauth, I'm getting the same error:
>>>
>>> eightkpc@objectstore1:~/s3curl$ ./s3curl.pl
>>> 
>>> --id=testerks -- http://127.0.0.1:8080/
>>> 
>>> 
>>> SignatureDoesNotMatchThe request signature
>>> we calculated does not match the signature you provided. Check your key and
>>> signing method.txa691e7ca97a44d56bc4c2-005b06a2
>>> 92
>>>
>>> May 24 11:31:30 localhost proxy-server: 127.0.0.1 127.0.0.1
>>> 24/May/2018/11/31/30 GET / HTTP/1.0 403 - curl/7.58.0 - - 277 -
>>> txa691e7ca97a44d56bc4c2-005b06a292 - 0.0200 - - 1527161490.543112040
>>> 1527161490.563107014 -
>>> May 24 11:31:30 localhost proxy-server: STDERR: 127.0.0.1 - -
>>> [24/May/2018 11:31:30] "GET / HTTP/1.1" 403 621 0.021979 (txn:
>>> txa691e7ca97a44d56bc4c2-005b06a292)
>>>
>>> eightkpc@objectstore1:~$ cat .s3curl
>>> %awsSecretAccessKeys = (
>>> tester => {
>>> id => 'test:tester',
>>> key => 'testing',
>>> },
>>> testerks => {
>>> id => 'e6289a1b5692461388d0597a4873d054',
>>> key => '88bb706887094696b082f008ba133ad7',
>>> },
>>> );
>>>
>>> eightkpc@objectstore1:~$ openstack ec2 credentials show
>>> e6289a1b5692461388d0597a4873d054
>>> ++--
>>> 
>>> --+
>>> | Field  | Value
>>>
>>>  |
>>> ++--
>>> 
>>> --+
>>> | access | e6289a1b5692461388d0597a4873d0
>>> 54
>>>  |
>>> | links  | {u'self': u'http://controller:5000/v3/us
>>> ers/d7df7b56343b4ea988869fc30efeda09/credentials/OS-EC2/e628
>>> 9a1b5692461388d0597a4873d054'} |
>>> | project_id | dc86f7d8787b46158268bd77098b65
>>> 78
>>>  |
>>> | secret | 88bb706887094696b082f008ba133a
>>> d7
>>>  |
>>> | trust_id   | None
>>>
>>>  |
>>> | user_id| d7df7b56343b4ea988869fc30efeda
>>> 09
>>>  |
>>> ++--
>>> 
>>> --+
>>>
>>> Can someone please let me know what is going on?
>>>
>>> Regards,
>>> Shyam
>>> ___
>>> Mailing list: https://eur03.safelinks.protec
>>> tion.outlook.com/?url=http%3A%2F%2Flists.openstack.org%
>>> 2Fcgi-bin%2Fmailman%2Flistinfo%2Fopenstack=02%7C01%7C%7
>>> C39742b8c6bf847ee381508d5c16d1b21%7C84df9e7fe9f640afb435
>>> %7C1%7C0%7C636627596701206160=KI%2F2T2FhVQJTeX
>>> 1KbIObDZVDiUA3SbTq6Pplo1bc7ak%3D=0
>>> Post to : 

Re: [Openstack] Struggling to get the s3 api interface to work with swift.

[Shyam Prasad N]

Thanks. I'll try this.
But what values do I use in place of ak and sk? I want to use some command
to get those values, right?

On Fri, May 25, 2018 at 9:52 AM, Yuxin Wang 
wrote:

> I created ec2 credentials using command `openstack credential create`.
>
> i.e.
>
> openstack credential create --type ec2 --project proj user '{"access":
> "ak", "secret": "sk”}'
>
>
> It seems the two credentials are not the same thing.
>
> Ref:
>
> https://www.ibm.com/support/knowledgecenter/en/STXKQY_4.1.
> 1/com.ibm.spectrum.scale.v4r11.adv.doc/bl1adv_
> ConfigureOpenstackEC2credentials.htm
>
> 在 2018年5月25日，10:32，Shyam Prasad N  写道：
>
> Yes, I did.
> I don't think this is s3curl related issue, because I tried with python
> AWS SDK, and got the same error.
>
> On Fri, May 25, 2018, 07:42 Yuxin Wang  wrote:
>
>> Did you add 127.0.0.1 to the endpoint list in s3curl.pl?
>>
>> i.e.
>>
>> my @endpoints = (‘127.0.0.1’);
>>
>> 在 2018年5月24日，19:48，Shyam Prasad N  写道：
>>
>> Hi,
>>
>> I've been trying to get swift3 to work for several days now. But I
>> haven't managed to get it running.
>> Both with tempauth and keystoneauth, I'm getting the same error:
>>
>> eightkpc@objectstore1:~/s3curl$ ./s3curl.pl
>> 
>> --id=testerks -- http://127.0.0.1:8080/
>> 
>> 
>> SignatureDoesNotMatchThe request signature
>> we calculated does not match the signature you provided. Check your key and
>> signing method.txa691e7ca97a44d56bc4c2-
>> 005b06a292
>>
>> May 24 11:31:30 localhost proxy-server: 127.0.0.1 127.0.0.1
>> 24/May/2018/11/31/30 GET / HTTP/1.0 403 - curl/7.58.0 - - 277 -
>> txa691e7ca97a44d56bc4c2-005b06a292 - 0.0200 - - 1527161490.543112040
>> 1527161490.563107014 -
>> May 24 11:31:30 localhost proxy-server: STDERR: 127.0.0.1 - -
>> [24/May/2018 11:31:30] "GET / HTTP/1.1" 403 621 0.021979 (txn:
>> txa691e7ca97a44d56bc4c2-005b06a292)
>>
>> eightkpc@objectstore1:~$ cat .s3curl
>> %awsSecretAccessKeys = (
>> tester => {
>> id => 'test:tester',
>> key => 'testing',
>> },
>> testerks => {
>> id => 'e6289a1b5692461388d0597a4873d054',
>> key => '88bb706887094696b082f008ba133ad7',
>> },
>> );
>>
>> eightkpc@objectstore1:~$ openstack ec2 credentials show
>> e6289a1b5692461388d0597a4873d054
>> ++--
>> 
>> --+
>> | Field  | Value
>>
>>  |
>> ++--
>> 
>> --+
>> | access | e6289a1b5692461388d0597a4873d0
>> 54
>>  |
>> | links  | {u'self': u'http://controller:5000/v3/users/
>> d7df7b56343b4ea988869fc30efeda09/credentials/OS-EC2/
>> e6289a1b5692461388d0597a4873d054'} |
>> | project_id | dc86f7d8787b46158268bd77098b65
>> 78
>>  |
>> | secret | 88bb706887094696b082f008ba133a
>> d7
>>  |
>> | trust_id   | None
>>
>>  |
>> | user_id| d7df7b56343b4ea988869fc30efeda
>> 09
>>  |
>> ++--
>> 
>> --+
>>
>> Can someone please let me know what is going on?
>>
>> Regards,
>> Shyam
>> ___
>> Mailing list: https://eur03.safelinks.protection.outlook.com/?url=
>> http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman%
>> 2Flistinfo%2Fopenstack=02%7C01%7C%7C39742b8c6bf847ee381508d5c16d
>> 1b21%7C84df9e7fe9f640afb435%7C1%7C0%
>> 7C636627596701206160=KI%2F2T2FhVQJTeX1KbIObDZVDiUA3SbT
>> q6Pplo1bc7ak%3D=0
>> Post to : openstack@lists.openstack.org
>> Unsubscribe : https://eur03.safelinks.protection.outlook.com/?url=
>> http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman%
>> 2Flistinfo%2Fopenstack=02%7C01%7C%7C39742b8c6bf847ee381508d5c16d
>> 1b21%7C84df9e7fe9f640afb435%7C1%7C0%
>> 7C636627596701206160=KI%2F2T2FhVQJTeX1KbIObDZVDiUA3SbT
>> q6Pplo1bc7ak%3D=0
>>
>>
>>
>


-- 
-Shyam
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : 

Re: [Openstack] Struggling to get the s3 api interface to work with swift.

[Kota TSUYUZAKI]

Hi, Shyam

> tester => {
> id => 'test:tester',
> key => 'testing',
> },

If you are using this id/password to get your token from keystone,
you should set them as access_key and secret key for your s3 client.
You don't have to set any token information from keystone for your client.
i.e. `./s3curl.pl --id=tester -- http://127.0.0.1:8080/` may work. I'm not
an expert of the s3curl client though.

Best,
Kota


(2018/05/24 20:48), Shyam Prasad N wrote:
> Hi,
> 
> I've been trying to get swift3 to work for several days now. But I haven't
> managed to get it running.
> Both with tempauth and keystoneauth, I'm getting the same error:
> 
> eightkpc@objectstore1:~/s3curl$ ./s3curl.pl --id=testerks --
> http://127.0.0.1:8080/
> 
> SignatureDoesNotMatchThe request signature we
> calculated does not match the signature you provided. Check your key and
> signing
> method.txa691e7ca97a44d56bc4c2-005b06a292
> 
> May 24 11:31:30 localhost proxy-server: 127.0.0.1 127.0.0.1
> 24/May/2018/11/31/30 GET / HTTP/1.0 403 - curl/7.58.0 - - 277 -
> txa691e7ca97a44d56bc4c2-005b06a292 - 0.0200 - - 1527161490.543112040
> 1527161490.563107014 -
> May 24 11:31:30 localhost proxy-server: STDERR: 127.0.0.1 - - [24/May/2018
> 11:31:30] "GET / HTTP/1.1" 403 621 0.021979 (txn:
> txa691e7ca97a44d56bc4c2-005b06a292)
> 
> eightkpc@objectstore1:~$ cat .s3curl
> %awsSecretAccessKeys = (
> tester => {
> id => 'test:tester',
> key => 'testing',
> },
> testerks => {
> id => 'e6289a1b5692461388d0597a4873d054',
> key => '88bb706887094696b082f008ba133ad7',
> },
> );
> 
> eightkpc@objectstore1:~$ openstack ec2 credentials show
> e6289a1b5692461388d0597a4873d054
> +++
> | Field  |
> Value
> |
> +++
> | access |
> e6289a1b5692461388d0597a4873d054
> |
> | links  | {u'self': u'
> http://controller:5000/v3/users/d7df7b56343b4ea988869fc30efeda09/credentials/OS-EC2/e6289a1b5692461388d0597a4873d054'}
> |
> | project_id |
> dc86f7d8787b46158268bd77098b6578
> |
> | secret |
> 88bb706887094696b082f008ba133ad7
> |
> | trust_id   |
> None
> |
> | user_id|
> d7df7b56343b4ea988869fc30efeda09
> |
> +++
> 
> Can someone please let me know what is going on?
> 
> Regards,
> Shyam
> 
> 
> 
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> 



___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack