On Oct 3, 2012, at 7:33 PM, Alan Pevec ape...@gmail.com wrote:
On Wed, Oct 3, 2012 at 8:31 AM, Dolph Mathews dolph.math...@gmail.com wrote:
At the very least, I'd like to move this approach to the end of the page;
and ideally, the script would be managed by openstack.
There's a sample
: [Openstack] Enabling logging in keystone.
No worries, that's what a second set of eyes is for!
By specifying a token and endpoint, you're bypassing the authentication process
that your curl command is performing.
You can test authentication with the keystone client using:
$ keystone --os-username
...@gmail.com]
*Sent:* Tuesday, October 02, 2012 2:19 PM
*To:* Ahmed Al-Mehdi
*Cc:* heckj; openstack@lists.launchpad.net
*Subject:* Re: [Openstack] Enabling logging in keystone.
No worries, that's what a second set of eyes is for!
By specifying a token and endpoint, you're bypassing
On Wed, Oct 3, 2012 at 8:31 AM, Dolph Mathews dolph.math...@gmail.com wrote:
At the very least, I'd like to move this approach to the end of the page;
and ideally, the script would be managed by openstack.
There's a sample script in Keystone
Subject: Re: [Openstack] Enabling logging in keystone.
Hi Joe,
Unfortunately before I read your response I re-installed my Ubuntu server. I
repeated the same steps mentioned in the OpenStack document Deploy and Install
OpenStack - RedHat Ubuntu and also used the script mentioned in it
(https
@lists.launchpad.net
Subject: Re: [Openstack] Enabling logging in keystone.
Hi Joe,
Unfortunately before I read your response I re-installed my Ubuntu server. I
repeated the same steps mentioned in the OpenStack document Deploy and
Install OpenStack - RedHat Ubuntu and also used the script mentioned
: openstack@lists.launchpad.net
Subject: Re: [Openstack] Enabling logging in keystone.
Hi Joe,
Unfortunately before I read your response I re-installed my Ubuntu server. I
repeated the same steps mentioned in the OpenStack document Deploy and
Install OpenStack - RedHat Ubuntu and also used
: [Openstack] Enabling logging in keystone.
You're missing a 5 on the admin_token you've specified on the command line.
012345SECRET99TOKEN01234 (your CLI arg)
012345SECRET99TOKEN012345 (keystone.conf)
-Dolph
On Tue, Oct 2, 2012 at 1:08 PM, Ahmed Al-Mehdi
ah...@coraid.commailto:ah...@coraid.com
[dolph.math...@gmail.com]
*Sent:* Tuesday, October 02, 2012 12:12 PM
*To:* Ahmed Al-Mehdi
*Cc:* heckj; openstack@lists.launchpad.net
*Subject:* Re: [Openstack] Enabling logging in keystone.
You're missing a 5 on the admin_token you've specified on the command
line.
012345SECRET99TOKEN01234
; openstack@lists.launchpad.net javascript:_e({}, 'cvml',
'openstack@lists.launchpad.net');
*Subject:* Re: [Openstack] Enabling logging in keystone.
You're missing a 5 on the admin_token you've specified on the command
line.
012345SECRET99TOKEN01234 (your CLI arg)
012345SECRET99TOKEN012345
@lists.launchpad.net
Subject: Re: [Openstack] Enabling logging in keystone.
Hi Ahmed -
I believe you don't have a tenant named adminTenant - possibly try this?
curl -d '{auth: {tenantName: service, passwordCredentials: {username:
adminUser, password: secretword}}}' -H Content-type: application/json
http
:* Dolph Mathews [dolph.math...@gmail.com]
*Sent:* Tuesday, October 02, 2012 12:12 PM
*To:* Ahmed Al-Mehdi
*Cc:* heckj; openstack@lists.launchpad.net
*Subject:* Re: [Openstack] Enabling logging in keystone.
You're missing a 5 on the admin_token you've specified on the
command line
@lists.launchpad.nethttps://exg5.exghost.com/owa/UrlBlockedError.aspx
Subject: Re: [Openstack] Enabling logging in keystone.
You're missing a 5 on the admin_token you've specified on the command line.
012345SECRET99TOKEN01234 (your CLI arg)
012345SECRET99TOKEN012345 (keystone.conf)
-Dolph
On Tue, Oct 2
:* Re: [Openstack] Enabling logging in keystone.
No worries, that's what a second set of eyes is for!
By specifying a token and endpoint, you're bypassing the authentication
process that your curl command is performing.
You can test authentication with the keystone client using:
$ keystone
; openstack@lists.launchpad.net
Subject: Re: [Openstack] Enabling logging in keystone.
No worries, that's what a second set of eyes is for!
By specifying a token and endpoint, you're bypassing the authentication
process that your curl command is performing.
You can test authentication
: Tuesday, October 02, 2012 4:50 PM
To: openstack@lists.launchpad.net
Cc: heckj; Ahmed Al-Mehdi; Anne Gentle
Subject: Re: [Openstack] Enabling logging in keystone.
I find it odd that the document describes two approaches for configuring
keystone -- one being a relatively undocumented, scripted
; Anne Gentle
*Subject:* Re: [Openstack] Enabling logging in keystone.
I find it odd that the document describes two approaches for configuring
keystone -- one being a relatively undocumented, scripted approach not
managed or distributed by OpenStack. Surely these two approaches will
continue
.
--
*From:* Dolph Mathews [dolph.math...@gmail.com]
*Sent:* Tuesday, October 02, 2012 2:19 PM
*To:* Ahmed Al-Mehdi
*Cc:* heckj; openstack@lists.launchpad.net
*Subject:* Re: [Openstack] Enabling logging in keystone.
No worries, that's what a second set of eyes
Hello,
I am trying to verify the installation of keystone. When I try to run some
curl commands, I get the following error message:
root@bodega:~/ahmed/keystone-init# curl -d '{auth: {tenantName:
adminTenant, passwordCredentials: {username: adminUser, password:
secretword}}}' -H
: [Openstack] Enabling logging in keystone.
Ahmed -
The header that's supposed to have the token within it is labelled
X-Auth-Token', not X_Auth_Token. Unless you're really comfortable with the
protocol, I'd recommend using the keystone CLI from the python-keystoneclient
to do your verifying, using
.
From: heckj he...@mac.com
Date: Monday, October 1, 2012 5:23 PM
To: Ahmed Al-Mehdi ah...@coraid.com
Cc: openstack@lists.launchpad.net openstack@lists.launchpad.net
Subject: Re: [Openstack] Enabling logging in keystone.
Ahmed -
The header that's supposed to have the token within
] Enabling logging in keystone.
Ahmed -
The header that's supposed to have the token within it is labelled
X-Auth-Token', not X_Auth_Token. Unless you're really comfortable with
the protocol, I'd recommend using the keystone CLI from the
python-keystoneclient to do your verifying, using it's
22 matches
Mail list logo