Given that 35357 is keystone's IANA assigned port, I don't think it's
reasonable to expect keystone to change ports in the short term. In the
long term (after dropping API v2 support), keystone will be deployable
on any one port. Using 35357 theoretically aids discoverability a tiny
bit, but there
Missed the documentation requirement in the last paragraph. 100% agree!
** Changed in: keystone
Status: Won't Fix => Triaged
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1253482
This has been previously discussed, and 404 is the preferred status code
for an invalid subject token, which must be distinguished from an
invalid X-Auth-Token. An invalid/revoked/expired X-Subject-Token CANNOT
be "considered similar to providing incorrect username or password" --
the requestor is
I'm not able to reproduce on master, and unfortunately folsom is now
unsupported. If this is reproducible on grizzly or havana, perhaps
there's something we can backport. That said, I suspect this issue
actually exists in the version of the python memcache client -- perhaps
it can be updated to som
Agree with morgan- you could address this on the client side, but
there's no way to handle this on the service side without tracking
session state in keystone.
** Changed in: keystone
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Enginee
keystone isn't capable of returning 503's itself... it also looks like
this is a failed request to swift.
** Also affects: swift
Importance: Undecided
Status: New
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Ya
Thanks, David!
** Changed in: python-keystoneclient
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1247752
Title:
Marker could not be
Unfortunately, we currently only support 0.7.x and are currently working
on supporting >=0.8.x in icehouse:
https://github.com/openstack/requirements/blob/a0acd133f3a005c81e555eadde9ad0a7f0236c0e
/global-requirements.txt#L94
If you have pip available, you might be able to upgrade with:
pip ins
Unfortunately, this slipped through the havana release without seeing a
fix, so it's now considered stable API and can't be removed. I can't
find it at the moment, but there is an effort being tracked in either a
bug or bp to start testing against additional attributes from leaking
into API objects
Folsom doesn't support this operation, as it was introduced in grizzly.
The call is basically:
PUT /v3/projects/{project_id}/groups/{group_id}/roles/{role_id}
Relevant API docs:
https://github.com/openstack/identity-api/blob/master/openstack-
identity-api/v3/src/markdown/identity-api-v3.md#
The above fix has not been released yet.
** Changed in: keystone
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1247142
Title:
Live LDAP te
Reverting the above patch as it caused subsequent issues when combined
with patchset 16 of https://review.openstack.org/#/c/50491/
After discussing the issue further, this bug report & patch doesn't
address the underlying issue which is that we're raising 400's based on
typeerrors in the first pla
This is, as you noted, out of scope for keystoneclient to fix.. unless
we were going to switch from argparse which is unlikely. This shortcut
behavior is by design in argparse; related discussion here:
http://bugs.python.org/issue14910
** Changed in: keystone
Status: New => Invalid
** A
Public bug reported:
The 'valid' index on the token table in the SQL driver doesn't appear to
be used. The 'expires' index is used, and the 'expires + valid' index is
used, but we never query on valid alone.
** Affects: keystone
Importance: Low
Status: New
--
You received this bug
Isn't this exposed on v3 but not documented... again?
** Also affects: openstack-api-site
Importance: Undecided
Status: New
** Changed in: keystone
Importance: Undecided => Wishlist
** Changed in: python-keystoneclient
Importance: Undecided => Wishlist
--
You received this bug
Sorry for the delayed response, but I believe this specific issue has
been fixed as part of one of the related bugs (correct me if I'm
mistaken):
https://bugs.launchpad.net/keystone/+bug/1221808
https://bugs.launchpad.net/keystone/+bug/1215192
Ongoing work is still being tracked in the follow
** Project changed: keystone => openstack-api-site
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1065614
Title:
Document APIs for PKI tokens
Status in OpenStack API documentation site
** Changed in: keystone
Status: New => Invalid
** Tags removed: grizzly-backport-potential havana-backport-potential
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1240170
Title:
** No longer affects: keystone
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1208286
Title:
V3 Identity API: expired tokens are not documented as invalid
Status in OpenStack API docum
Was going to mark this as invalid, but the above configuration should
definitely be documented.
** Changed in: keystone
Status: Incomplete => Invalid
** Changed in: keystone
Status: Invalid => Confirmed
** Changed in: keystone
Importance: Undecided => Medium
--
You received th
Public bug reported:
The new gate check against unexpected "ERRORs" appearing in logs
actually caught the string "ERROR" in a PKI token in the second jenkins
run of the first patchset in:
https://review.openstack.org/#/c/61419/
If you search the log output, you'll find the string "ERROR" burie
Moved to oslo as there's nothing keystone-specific about this.
** Changed in: keystone
Importance: Undecided => Wishlist
** Project changed: keystone => oslo
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bu
Keystone does not yet support multiple workers. There's a patch from
late in the havana cycle to introduce it, however.
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone
Yep! It looks like the move to six resolved this.
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1239956
Title:
Remove obsolete co
The admin_token does not represent a user and carries no explicit
authorization that can be delegated. It's just a magical hack for
bootstrapping keystone and should be removed from the wsgi pipeline
after that.
** Changed in: keystone
Status: Confirmed => Invalid
--
You received this bug
If the migration can't be applied, then it should exit cleanly without
making changes (an inconsistent state is a terrible place to be!).
I think the migration should wait for manual intervention to correct
unexpected data (duplicate service names). Adding devstack to this bug
because it sounds li
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1261572
Title:
Keystoneclient import fails in python3
Status in OpenStack Identity
** Changed in: keystone
Importance: Undecided => Medium
** Changed in: keystone
Status: New => Confirmed
** Project changed: keystone => openstack-api-site
** Tags added: identity-api
** Summary changed:
- Keystone v3 documentation is lacking w.r.t. Domain Token authentication
+ Keys
The warning line is just that - a warning. You must have a token and
endpoint in your environment (there are deprecated environment variables
names that are still supported that could be in use). However, in the
case of token-get, using a token & endpoint is actually the cause of
"'NoneType' object
As of icehouse, this is now by design. We're working to increase the
separation between the assignments and identity backends, and as a
result, have opted to not validate entities from the identity backend
(users, groups) in the assignment backend, and vice versa.
This issue described here is an u
keystone.contrib.access:AccessLogMiddleware already does this -- include
it in your pipeline and configure it's output per the example in
logging.conf.sample:
https://github.com/openstack/keystone/blob/master/etc/logging.conf.sample
** Changed in: keystone
Status: New => Invalid
--
You r
** Changed in: keystone
Status: Fix Released => In Progress
** Changed in: keystone
Assignee: David Stanek (dstanek) => Ilya Pekelny (i159)
** Changed in: keystone
Milestone: icehouse-2 => None
--
You received this bug notification because you are a member of Yahoo!
Engineering
The XML here appears to be as specified by https://github.com/openstack
/identity-api/blob/master/openstack-identity-
api/v2.0/src/docbkx/xsd/token.xsd
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
As of keystone stable/havana 2013.2.2 (commit
0d83e7eee20a50a75863a9d3c75aee7030518229), this doesn't appear to be an
issue. I attempted to reproduce with:
$ python -c "import json; print
json.dumps(json.loads(open('etc/policy.v3cloudsample.json').read()),
indent=2)"
But got pretty-printed JSON a
Public bug reported:
policy.json and policy.v3cloudsample.json are both missing entries for
the new /v3/regions operations.
** Affects: keystone
Importance: Medium
Assignee: Dolph Mathews (dolph)
Status: New
--
You received this bug notification because you are a member of
gions
PUT /v3/regions/{region_id}
** Affects: keystone
Importance: Medium
Assignee: Dolph Mathews (dolph)
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpa
I'm not sure what you're expecting here? You intentionally put garbage
data into keystone's configuration and it's appropriately reporting an
error against that data. You can bypass the authentication process by
using keystone.conf [DEFAULT] admin_token instead of trying to use
credentials and cons
The internal URL isn't intended to be secret or privileged. It's
intended to be a public endpoint on an internal (unmetered) network
interface.
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which i
Marking this as invalid because I think this is expected behavior for
keystone. If a user does get themselves into this situation, the static
admin_token defined by keystone.conf is intended exactly for this
scenario- bootstrapping an admin user (or in this case, re-bootstrapping
an admin user).
*
Marking this as invalid for keystone as I believe this issue was caused
by keystoneclient and is now fixed. Please re-open if I'm mistaken.
** Changed in: keystone
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which i
Domains, services and endpoints support 'enabled' on v3. Credentials and
groups do not. I'm not sure there's any value in toggling an
enable/disable on those entities? Either way, this should be a BP
explaining the desired impact of disabling those entities.
** Changed in: keystone
Status:
Marking this as wont-fix because A) we can't really change that API
anymore, and B) v3 has been implemented with a /v3/credentials API,
which is (in part) intended to replace the EC2 v2 extension along with
pluggable auth (we also haven't implemented an ec2 plugin yet). The
above google doc has mov
Moving this issue to a BP:
https://blueprints.launchpad.net/keystone/+spec/keystone-manage-token-
flush
** Changed in: keystone
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://
Managers act as common proxies to drivers. See
keystone.catalog.core.Manager for an example of their value.
** Changed in: keystone
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://
>From the cited link: "Names of built-in functions are permitted as
identifiers but may require care to be used as such." "A reserved word
can be used as an identifier if you quote it."
** Changed in: keystone
Status: New => Won't Fix
--
You received this bug notification because you are
The user running keystone should (in *most* cases) not be capable of
creating and properly assigning permissions to the non-existant
directory.
I'd also argue that the currently provided error message is fairly
explicit in indicating that the directory is not writable (No such file
or directory: '
I'm not quite sure what the bug is here (what's "invalid"?) but I'm
hoping the following will resolve any confusion:
- Ideally unversioned endpoints should be provided to keystone, which in turn
passes them to clients.
- The service catalog should not have any awareness of versioned endpoints
- C
Marking as wont-fix since this is a mysql permissions issue; if this
hasn't been resolved, I'd suggest pinging the mailing list.
** Changed in: keystone
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed
The KeyError here is indicating that your public_url contains something
like %(tenant-id)s which should instead be %(tenant_id)s
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
Sounds like this is resolved? auth_token has been moved to
keystoneclient in Grizzly.
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.lau
This appears to be two separate issues, the first of which is by design.
Users do not have roles without requesting authorization on a tenant,
but we're working towards supporting domain-admins, etc, to make the
semantic more meaningful.
On the second issue by "show a warning", are you referri
I'd be happy to see the identity API amended with an acknowledged
("reserved") list of credential types, but there's no way for keystone
to enforce or validate that list, as it would break deployments
attempting to use proprietary types, or from existing deployments to
support future clients, etc.
Unassigning as I assume this isn't being pursued anymore.
With the introduction of oslo, this sounds like a great common
middleware that could be deployed on top of any openstack service as
needed.
** Changed in: keystone
Status: In Progress => Won't Fix
** Changed in: keystone
Assig
While this v2 API is still not implemented AFAIK, we've introduced the
ability to list roles between user-project pairs, group-project pairs,
user-domain pairs, and group-domains pairs... which obviously goes well
beyond the murky functionality of this v2 call.
** Changed in: keystone
Statu
You're running in debug mode :)
Set debug = false in keystone.conf and the details of authentication
failures will be suppressed.
** Changed in: keystone
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subsc
This is by design; disable debug mode to suppress the details of auth
failures from the API.
Please re-open if debug is already False.
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscr
The v3 API specifies a different links structure than that used by v2.
See the "links" section on:
https://github.com/openstack/identity-api/blob/master/openstack-
identity-api/src/markdown/identity-api-v3.md#required-attributes
Several examples in the API doc illustrate their use.
** Changed
No, it's not the same data and you probably shouldn't have authz there
for this use case. By design, v3 is intending to correct a very strange
behavior in the v2 API. That is, the following call is used by users to
list tenants to which they have access:
http://identity:5000/v2.0/tenants
Admini
Looking at this again, I'm not sure that the InvocationError should be
caught? It looks like the invocation of PEP8 is failing as it should
(there's a PEP8 violation causing the command to return non-zero).
** Changed in: keystone
Status: New => Invalid
--
You received this bug notificati
For better or worse, I'll take credit for this decision.
The format used by /v3/auth is actually preferred, as it's a bit more
forward-looking. The primary benefit is that links can be provided on
nested objects along with various identification methods in requests
(which follow the same syntax di
Hmm, that seems valid -- I'll try to reproduce.
** Changed in: keystone
Status: Invalid => Triaged
** Changed in: keystone
Importance: Undecided => Low
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://b
A couple notes:
--pep-8 is not an option
--pep8 is redundant with -p
However, I'm unable to reproduce on master with pep8 version 1.3.3 as
specified by tools/tests-requires:
http://paste.openstack.org/raw/33604/
Are you sure you're using pep8 1.3.3 locally?
** Changed in: keystone
: so I can't reproduce that issue. Generated a token for admin
from curl localhost:5000/v2.0/token and it seems to work for everything.
** Changed in: keystone
Status: Incomplete => Invalid
** Changed in: keystone
Milestone: grizzly-rc1 => None
--
You received this bug notification b
Assuming this is now unreproducible on master -- please re-open if I'm
mistaken.
** Changed in: keystone
Status: Incomplete => Invalid
** Changed in: keystone
Milestone: grizzly-rc1 => None
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, whi
I agree that the *_api convention is not super helpful, but identity_api
is actually a reference to the instantiated driver, not a reference to
the identity manager or the controller. Renaming those references to
*_controller would actually be even more misleading. We also have tests
against both m
This is by design; is there a specific aspect of the XML you'd like to
see changed?
** Changed in: keystone
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/
A similar proposal is also being tracked in a different blueprint:
https://blueprints.launchpad.net/keystone/+spec/keystone-manage-token-
flush
Closing this bug as the two blueprints are sufficient for tracking.
** Changed in: keystone
Status: New => Invalid
--
You received this bug n
It appears that we have sqlalchemy and sqlalchemy migrate pinned
appropriately:
https://github.com/openstack/keystone/blob/master/tools/pip-requires
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
auth_token has been moved from keystone.middleware.auth_token to
keystoneclient.middleware.auth_token
The docs you're referring to (2013.1 / grizzly?) appear to be ahead of
the version of keystone you're trying to install (2012.2 / folsom?).
** Changed in: keystone
Status: New => Invalid
** Changed in: keystone/folsom
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1176204
Title:
keystone ipv6 tests fail
Status in OpenStack Identity (Keysto
Similar answer from the keystone side - we're getting further away from
the "default project" thing. In v3, we're viewing a user's default
project as simply a user-defined preference: the project which the user
should authorize against if the user didn't request a specific project.
User-Project as
Marking this as invalid (not sure how else to mark it), but it's
actually superceded by a blueprint targeted to havana-m1:
https://blueprints.launchpad.net/keystone/+spec/keystone-manage-token-
flush
** Changed in: keystone
Status: Expired => New
** Changed in: keystone
Status: N
** Changed in: python-keystoneclient
Milestone: None => 0.2.4
** Changed in: python-keystoneclient
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.n
** Changed in: python-keystoneclient
Milestone: None => 0.2.0
** Changed in: python-keystoneclient
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.n
** Changed in: python-keystoneclient
Milestone: None => 0.2.4
** Changed in: python-keystoneclient
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.n
** Changed in: python-keystoneclient
Status: Fix Committed => Fix Released
** Changed in: python-keystoneclient
Milestone: None => 0.2.3
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to quantum.
https://bugs.launchpad.ne
** Changed in: python-keystoneclient
Milestone: None => 0.2.4
** Changed in: python-keystoneclient
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.n
** Changed in: python-keystoneclient
Status: Fix Committed => Fix Released
** Changed in: python-keystoneclient
Milestone: None => 0.2.0
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to quantum.
https://bugs.launchpad.ne
** Changed in: python-keystoneclient
Milestone: None => 0.2.4
** Changed in: python-keystoneclient
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://
** Changed in: python-keystoneclient
Milestone: None => 0.2.0
** Changed in: python-keystoneclient
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.n
** Changed in: python-keystoneclient
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1048662
Title:
Add an option to disable a service
Statu
** Changed in: python-keystoneclient
Milestone: None => 0.2.1
** Changed in: python-keystoneclient
Status: Fix Committed => Fix Released
** Changed in: python-keystoneclient
Importance: Undecided => Low
--
You received this bug notification because you are a member of Yahoo!
Engin
** Changed in: python-keystoneclient
Importance: Undecided => High
** Changed in: python-keystoneclient
Milestone: None => 0.2.3
** Changed in: python-keystoneclient
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engi
** Changed in: python-keystoneclient
Importance: Undecided => Medium
** Changed in: python-keystoneclient
Status: Fix Committed => Fix Released
** Changed in: python-keystoneclient
Milestone: None => 0.2.1
--
You received this bug notification because you are a member of Yahoo!
En
** Changed in: python-keystoneclient
Milestone: None => 0.2.3
** Changed in: python-keystoneclient
Status: Fix Committed => Fix Released
** Changed in: python-keystoneclient
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Yahoo!
En
** Changed in: python-keystoneclient
Milestone: None => 0.2.4
** Changed in: python-keystoneclient
Status: Fix Committed => Fix Released
** Changed in: python-keystoneclient
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Yahoo!
En
** Changed in: python-keystoneclient
Importance: Undecided => Medium
** Changed in: python-keystoneclient
Status: Fix Committed => Fix Released
** Changed in: python-keystoneclient
Milestone: None => 0.2.4
--
You received this bug notification because you are a member of Yahoo!
En
** Changed in: python-keystoneclient
Importance: Undecided => Medium
** Changed in: python-keystoneclient
Status: Fix Committed => Fix Released
** Changed in: python-keystoneclient
Milestone: None => 0.2.4
--
You received this bug notification because you are a member of Yahoo!
En
Fixed in https://github.com/openstack/python-
keystoneclient/commit/d202da568441341f4f6abce2894016164a0562e0
** Changed in: python-keystoneclient
Milestone: None => 0.2.4
** Changed in: python-keystoneclient
Status: In Progress => Fix Committed
** Changed in: python-keystoneclient
Looks like keystone's API is behaving as expected.
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1161963
Title
See the exception:
H302 import only modules.'from keystone.openstack.common.gettextutils
import _' does not import a module
'_' is not a module
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, whi
The core issue in this bug is addressed and implemented as part of the
above blueprint. Indexes are being tracked separately, and an index on
valid has already been merged.
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yah
** Changed in: keystone
Status: Incomplete => Invalid
** Converted to question:
https://answers.launchpad.net/keystone/+question/230192
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1115284
Title:
StackTrace on 2012.1.4 middleware when storing token in memcache with
This was fixed by Brant at some point in the past month or so.
** Changed in: keystone
Importance: Undecided => Medium
** Changed in: keystone
Status: New => Fix Released
** Changed in: keystone
Assignee: (unassigned) => Brant Knudson (blk-u)
--
You received this bug notificatio
* Changed in: keystone
Status: Confirmed => In Progress
** Changed in: keystone
Assignee: (unassigned) => Dolph Mathews (dolph)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/118
** Changed in: keystone
Status: New => Invalid
** Changed in: keystone/folsom
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1183019
Title:
te
Apologies! I think the v3 spec have been clarified quite a bit since
this was bug was opened. The example call in the bug description would
be expected to raise a 404 because it doesn't match the spec:
https://github.com/openstack/identity-api/blob/master/openstack-
identity-api/src/markdown/ident
ayoung looks to be correct
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1174844
Title:
DELETE /v2.0/tokens/{token_id} should rem
This looks to be configurable in grizzly, but doesn't look to be
backportable to folsom, as we can't backport features.
** Changed in: keystone
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keysto
101 - 200 of 619 matches
Mail list logo
