V3 token fails with KeyError 'expires'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-keystoneclient |
Fix Released
|
High
|
Brant Knudson | ||
tempest |
Fix Released
|
Undecided
|
Brant Knudson |
Bug Description
If I get a token using the V3 API and then pass that token to nova, it fails with a 401 error.
A valid token generated using the V3 API shoud work with nova.
The stack trace in n-api looks like this:
2013-03-28 17:06:32 DEBUG [keystoneclient
Traceback (most recent call last):
File "/opt/stack/
self.
File "/opt/stack/
timestamp = data['token'
KeyError: 'expires'
I'm using devstack and have not changed the config.
Here's the command to get a token:
curl -i \
-d '
{
"auth": {
"identity": {
"methods": [ "password" ],
"password": {
"user": {
}
}
},
"scope": {
"project": {
"name": "admin"
}
}
}
}' \
-H "Content-Type: application/json" \
http://
Then I pass it on to nova (I get the token ID from the header, and put it in TOKEN_V3=).
curl \
-H "X-Auth-Token: $TOKEN_V3" \
http://
I also tried with a V2 token, which works.
Changed in keystone: | |
status: | New → Incomplete |
affects: | keystone → python-keystoneclient |
no longer affects: | keystone |
Changed in tempest: | |
status: | New → In Progress |
tags: | added: grizzly-rc-potential |
tags: | removed: grizzly-rc-potential |
Changed in python-keystoneclient: | |
milestone: | none → 0.2.4 |
importance: | Undecided → High |
status: | Fix Committed → Fix Released |
I didn't find a review in openstack either... maybe the problem is the token format and not the auth_token middleware?