Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id CF582200C56 for ; Fri, 14 Apr 2017 18:31:10 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id CDE74160B8C; Fri, 14 Apr 2017 16:31:10 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 451E3160B8A for ; Fri, 14 Apr 2017 18:31:10 +0200 (CEST) Received: (qmail 31664 invoked by uid 500); 14 Apr 2017 16:31:09 -0000 Mailing-List: contact user-help@jclouds.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@jclouds.apache.org Delivered-To: mailing list user@jclouds.apache.org Received: (qmail 31655 invoked by uid 99); 14 Apr 2017 16:31:09 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Apr 2017 16:31:09 +0000 Received: from sherlock (unknown [136.24.30.124]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 291151A00A6 for ; Fri, 14 Apr 2017 16:31:09 +0000 (UTC) Date: Fri, 14 Apr 2017 09:31:03 -0700 From: Andrew Gaul To: user@jclouds.apache.org Subject: Re: Openstack-Swift Message-ID: <20170414163103.GA19305@sherlock> References: <73E98F16-F29B-45DF-8289-796E5F71050E@emc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <73E98F16-F29B-45DF-8289-796E5F71050E@emc.com> User-Agent: Mutt/1.5.21 (2010-09-15) archived-at: Fri, 14 Apr 2017 16:31:11 -0000 Why don't you use the rackspace-cloudfiles-us provider which sets up authentication for you? On Thu, Apr 13, 2017 at 10:30:14PM +0000, Paya, Ashkan wrote: > Hello, > > We want to verify access to our openstack-swift account under Rackspace via “apiAccessKeyCredential” keystone authentication type. Our credentials are valid and we can issue the following curl command successfully and receive tokenId, tenant name and Id and etc. > > * curl https://identity.api.rackspacecloud.com/v2.0/tokens \ > * -X POST \ > * -d '{"auth":{"RAX-KSKEY:apiKeyCredentials":{"username”:”${USER}","apiKey":”${APIKEY}"}}}' \ > * -H "Content-type: application/json" | python -m json.tool > > Now, when we configure our BlobStoreContext object using the same parameters (endpoint, keystone auth type and etc) and trying to get the RegionScopedBlobStoreContext form it, we receive the following response: > > * Failed in command: …., org.jclouds.http.HttpResponseException: command: POST https://identity.api.rackspacecloud.com/v2.0/tokens HTTP/1.1 failed with response: HTTP/1.1 400 Bad Request; content: [{"badRequest":{"code":400,"message":"Invalid json request body"}}] > > In which they explain 400 as “Missing required parameters. This error also occurs if you include both the tenant name and ID in the request.”. Has anyone else experienced the same scenario or have some insight to share? > > Thank you, > Ashkan -- Andrew Gaul http://gaul.org/