Bingo! Thought that backslash was part of the swift key, gee! Thanks, Yehuda!
On Feb 24, 2014, at 1:27 PM, Yehuda Sadeh <yeh...@inktank.com> wrote: > On Mon, Feb 24, 2014 at 1:00 PM, Liu, Larry <larry....@disney.com> wrote: >> Sorry Yehuda, >> >> I tried all possible urls but either get access denied or 403 forbidden. >> >> curl -v -H 'X-Auth-user:<myuser>:swift' -H 'X-Auth-Key: >> 29q1tsCgx0Sft0j\/PJTcQSYk31MxxYMbaoryI4JM' http://myradosgw.domain/auth > > Remove the backslash from the key. > > Yehuda > >> * About to connect() to myradosgw.domain port 80 (#0) >> * Trying 10.190.10.18... connected >>> GET /auth HTTP/1.1 >>> User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0 >>> OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3 >>> Host: myradosgw.domain >>> Accept: */* >>> X-Auth-user:myuser:swift >>> X-Auth-Key: 29q1tsCgx0Sft0j\/PJTcQSYk31MxxYMbaoryI4JM >>> >> < HTTP/1.1 403 Forbidden >> < Date: Mon, 24 Feb 2014 20:51:11 GMT >> < Server: Apache/2.2.22 (Ubuntu) >> < Accept-Ranges: bytes >> < Content-Length: 23 >> < Content-Type: application/json >> < >> * Connection #0 to host myradosgw.domain left intact >> * Closing connection #0 >> {"Code":"AccessDenied"} >> >> >> This one gets nothing but 204 response : >> >> curl -v -H 'X-Auth-User: myuser:swift' -H 'X-Auth-Key: >> 29q1tsCgx0Sft0j\/PJTcQSYk31MxxYMbaoryI4JM' http://myradosgw.domain/swift/v1 >> * About to connect() to myradosgw.domain port 80 (#0) >> * Trying 10.190.10.18... connected >>> GET /swift/v1 HTTP/1.1 >>> User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0 >>> OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3 >>> Host: myradosgw.domain >>> Accept: */* >>> X-Auth-User: myuser:swift >>> X-Auth-Key: 29q1tsCgx0Sft0j\/PJTcQSYk31MxxYMbaoryI4JM >>> >> < HTTP/1.1 204 No Content >> < Date: Mon, 24 Feb 2014 20:55:28 GMT >> < Server: Apache/2.2.22 (Ubuntu) >> < Vary: Accept-Encoding >> < Content-Type: text/plain; charset=utf-8 >> < >> * Connection #0 to host u1304test001.compliant.disney.private left intact >> * Closing connection #0 >> >> Note, swift api client works just fine: >> >> swift -A http://myradosgw.domain/auth -U myuser:swift -K >> 29q1tsCgx0Sft0j\/PJTcQSYk31MxxYMbaoryI4JM list >> AAA >> AAB >> test >> >> >> >> >> >> >> >> >> >> >> >> On 2/24/14 12:32 PM, "Yehuda Sadeh" <yeh...@inktank.com> wrote: >> >>> See my last (and much overdue) response to Tim. >>> >>> Yehuda >>> >>> On Mon, Feb 24, 2014 at 12:14 PM, Liu, Larry <larry....@disney.com> wrote: >>>> Tim, has this been resolved? I'm having the same issue. No one seems to >>>> have >>>> an answer. Guess we just have to stick to using swift client util pkg. >>>> >>>> From: <Snider>, Tim <tim.sni...@netapp.com> >>>> Date: Friday, October 4, 2013 11:37 AM >>>> To: "ceph-users@lists.ceph.com" <ceph-users@lists.ceph.com> >>>> Subject: [ceph-users] ceph access using curl >>>> >>>> I'm having pilot error with getting the path correct using curl. >>>> >>>> Bucket listing using "radosgw-admin bucket list" works as does the swift >>>> API. >>>> >>>> Can someone point out my (obvious) error? >>>> >>>> >>>> >>>> Bucket list works: >>>> >>>> root@controller21:/home/ceph/my-cluster# radosgw-admin bucket list >>>> >>>> 2013-10-04 11:28:13.144065 7fe5f26fe780 0 WARNING: cannot read region >>>> map >>>> >>>> [ >>>> >>>> "xxx"] >>>> >>>> >>>> >>>> Swift API to Ceph works >>>> >>>> swift -V 1.0 -A >>>> http://ictp-R2C4-Controller21.ict.englab.netapp.com/auth -U rados:swift >>>> -K >>>> "xxx" stat >>>> >>>> Account: v1 >>>> >>>> Containers: 1 >>>> >>>> Objects: 1 >>>> >>>> Bytes: 604 >>>> >>>> Vary: Accept-Encoding >>>> >>>> Server: Apache/2.2.22 (Ubuntu) >>>> >>>> X-Account-Bytes-Used-Actual: 4096 >>>> >>>> Content-Type: text/plain; charset=utf-8 >>>> >>>> root@controller21:/home/ceph/my-cluster# swift -V 1.0 -A >>>> http://ictp-R2C4-Controller21.ict.englab.netapp.com/auth -U rados:swift >>>> -K >>>> "77iJvemrxWvYk47HW7pxsL+eHdA53AtLl2T0OyuG" list >>>> >>>> xxx >>>> >>>> >>>> >>>> However I can't get the correct http path. Variations of auth/v1.0, >>>> auth/v1 >>>> ... don't work either: >>>> >>>> root@controller21:/home/ceph/my-cluster# curl -v -H >>>> 'X-Storage-User: >>>> rados:swift' -H 'X-Storage-Pass: xxx' >>>> http://ictp-R2C4-Controller21.ict.englab.netapp.com/auth >>>> >>>> * About to connect() to >>>> ictp-R2C4-Controller21.ict.englab.netapp.com >>>> port 80 (#0) >>>> >>>> * Trying 10.113.193.189... connected >>>> >>>>> GET /auth HTTP/1.1 >>>> >>>>> User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0 >>>> OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3 >>>> >>>>> Host: ictp-R2C4-Controller21.ict.englab.netapp.com >>>> >>>>> Accept: */* >>>> >>>>> X-Storage-User: rados:swift >>>> >>>>> X-Storage-Pass: 77iJvemrxWvYk47HW7pxsL+eHdA53AtLl2T0OyuG >>>> >>>>> >>>> >>>> < HTTP/1.1 403 Forbidden >>>> >>>> < Date: Fri, 04 Oct 2013 18:30:01 GMT >>>> >>>> < Server: Apache/2.2.22 (Ubuntu) >>>> >>>> < Accept-Ranges: bytes >>>> >>>> < Content-Length: 23 >>>> >>>> < Content-Type: application/json >>>> >>>> < >>>> >>>> * Connection #0 to host >>>> ictp-R2C4-Controller21.ict.englab.netapp.com >>>> left intact >>>> >>>> * Closing connection #0 >>>> >>>> {"Code":"AccessDenied"}root@controller21:/home/ceph/my-cluster# >>>> >>>> >>>> >>>> Thanks, >>>> >>>> Tim >>>> >>>> >>>> _______________________________________________ >>>> ceph-users mailing list >>>> ceph-users@lists.ceph.com >>>> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com >>>> >>
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
