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 D2B2C200B9C for ; Mon, 10 Oct 2016 12:10:12 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D13AD160AE1; Mon, 10 Oct 2016 10:10:12 +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 1A984160ACA for ; Mon, 10 Oct 2016 12:10:11 +0200 (CEST) Received: (qmail 61405 invoked by uid 500); 10 Oct 2016 10:10:11 -0000 Mailing-List: contact dev-help@brooklyn.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@brooklyn.apache.org Delivered-To: mailing list dev@brooklyn.apache.org Received: (qmail 61394 invoked by uid 99); 10 Oct 2016 10:10:11 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Oct 2016 10:10:11 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id B5702E0159; Mon, 10 Oct 2016 10:10:10 +0000 (UTC) From: andreaturli To: dev@brooklyn.apache.org Reply-To: dev@brooklyn.apache.org References: In-Reply-To: Subject: [GitHub] brooklyn-server issue #374: BROOKLYN-358: karaf includes jclouds-api-swift Content-Type: text/plain Message-Id: <20161010101010.B5702E0159@git1-us-west.apache.org> Date: Mon, 10 Oct 2016 10:10:10 +0000 (UTC) archived-at: Mon, 10 Oct 2016 10:10:13 -0000 Github user andreaturli commented on the issue: https://github.com/apache/brooklyn-server/pull/374 I suspect `openstack-swift` is designed with the assumption that the provider will offer at least keystone v2 api (which are already deprecated!) SL still uses v1 so POST /tokens is not available that's why the authN fails. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---