Fixed in
https://review.openstack.org/#/c/118913/1/keystone/common/base64utils.py
** Changed in: keystone
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/b
This isn't a useful bug report, especially given that there's no useful
information here about the actual typo you're referring to. Happy to see
typos fixed without a bug report.
** Changed in: keystone
Importance: Undecided => Low
** Changed in: keystone
Status: In Progress => Invalid
*** This bug is a duplicate of bug 1312221 ***
https://bugs.launchpad.net/bugs/1312221
** This bug has been marked a duplicate of bug 1312221
Add user objects to mapping rules examples in OS-FEDERATION docs
--
You received this bug notification because you are a member of Yahoo!
Engineeri
We'd also have to not allow the current user to delete themselves, nor
the user to remove their last role assignment from the current scope,
etc. I'm all in favor of UX, but I also prefer the power to shoot myself
in the foot if I so choose. If we "fixed" this, I guarantee we'd get a
subsequent bug
** 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/1361378
Title:
"MySQL server has gone away" again
Status in OpenStack Identity (Key
** Project changed: keystone => horizon
--
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/1365458
Title:
Keystone auth needs a way to propogate some error message base
*** This bug is a duplicate of bug 1230279 ***
https://bugs.launchpad.net/bugs/1230279
** This bug has been marked a duplicate of bug 1230279
malformed endpoint URLs are destroying the API
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
** Changed in: keystone
Importance: Undecided => Low
** Changed in: keystone
Status: New => Triaged
** Also affects: openstack-api-site
Importance: Undecided
Status: New
** Tags added: low-hanging-fruit
--
You received this bug notification because you are a member of Yahoo
PKI is optional, hence it's an extension. Albeit, they are basically
only used for PKI, so a PKI namespace would have been preferable.
** Changed in: keystone
Status: New => Invalid
** Tags added: pki
--
You received this bug notification because you are a member of Yahoo!
Engineering Te
*** This bug is a duplicate of bug 1347891 ***
https://bugs.launchpad.net/bugs/1347891
** This bug has been marked a duplicate of bug 1347891
mis-use of XML canonicalization in keystone tests
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
Public bug reported:
Our last sync with openstack/requirements was around the beginning of
August. We haven't been able to sync because we have unit test failures
on the sync job since around August 20th:
https://review.openstack.org/#/c/111620/
Likely, our tests need to be fixed to support wh
I stand corrected. Keystone has the fix above in master as of 94efafd6
https://review.openstack.org/#/c/114863/
** Changed in: keystone
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
** Changed in: keystone
Status: Confirmed => 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/1252341
Title:
Horizon crashes when removing logged user from project
Statu
This looks like it was a packaging issue. If it's still a problem, I'd
suggest filing it against centos / RDO.
** 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:/
Public bug reported:
If a project or endpoint group is deleted, the endpoint grouping
extension should respond by deleting associated data. Instead, stale
data remains in the backend.
** Affects: keystone
Importance: Medium
Assignee: Bob Thyne (bob-thyne)
Status: In Progress
-
This has been addressed on the Keystone side with the above BP.
** Changed in: keystone
Status: Triaged => Invalid
** Changed in: keystone
Milestone: juno-3 => None
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keyst
** Also affects: neutron
Importance: Undecided
Status: New
** Also affects: horizon
Importance: Undecided
Status: New
** Also affects: swift
Importance: Undecided
Status: New
** Changed in: horizon
Status: New => Fix Committed
** No longer affects: horizon
** Also affects: python-keystoneclient
Importance: Undecided
Status: New
** Also affects: keystonemiddleware
Importance: Undecided
Status: New
** Changed in: keystone
Assignee: (unassigned) => Dolph Mathews (dolph)
** Changed in: python-keystoneclient
Assig
See bug 1365061 instead.
** Changed in: blazar
Status: Triaged => Invalid
** Changed in: glance
Status: In Progress => Invalid
** Changed in: keystone
Status: In Progress => Invalid
** Changed in: trove
Status: In Progress => Invalid
** Changed in: python-cinderclie
Public bug reported:
Contrary to bug 1285478, requirements files should not be sorted
alphabetically. Given that requirements files can contain comments, I'd
suggest a header in all requirements files along the lines of:
# The order of packages is significant, because pip processes them in the or
** Also affects: python-keystoneclient
Importance: Undecided
Status: New
** Changed in: python-keystoneclient
Assignee: (unassigned) => Sergey Kraynev (skraynev)
** Changed in: python-keystoneclient
Status: New => In Progress
--
You received this bug notification because y
Public bug reported:
This is a regression of an old issue, which I thought was resolved by
the "SELECT 1;" hack, but perhaps recently reintroduced with oslo.db?
[Mon Aug 25 14:30:54.403538 2014] [:error] [pid 25778:tid 139886259214080]
25778 ERROR keystone.common.wsgi [-] (OperationalError) (200
** Also affects: keystone/icehouse
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1347891
Title:
mis-use of XML canonicalization in keystone
*** This bug is a duplicate of bug 871822 ***
https://bugs.launchpad.net/bugs/871822
This is identical to bug 871822, regardless of the project consuming
eventlet.
** This bug has been marked a duplicate of bug 871822
nova-api crashed with input/output error
--
You received this bug noti
*** This bug is a duplicate of bug 871822 ***
https://bugs.launchpad.net/bugs/871822
This almost looks like a bug in Eventlet, or perhaps just poor feedback
from eventlet about the state of the machine it's running on? In
Keystone's case, you could avoid this by deploying to Apache httpd
inste
This is certainly expected behavior - Henry's explanation looks spot on,
and (2) explains the justification for the current behavior.
** Changed in: keystone
Status: New => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscrib
Adding keystone here then, so we can switch from the shell version
(which does not work on OS X) to the python version (which does work on
OS X).
** Also affects: keystone
Importance: Undecided
Status: New
** Changed in: keystone
Status: New => Triaged
** Changed in: keystone
In one request, you're referencing a role by name ("member", which is
valid), and in another request, you're trying to get a role by ID - and
there's certainly no role with id=member (id's are generally UUIDs).
GET /v3/roles?name=member should allow you to find the role ID by name.
** Changed in:
Leaving this as Opinion for the moment, because this was actually by
design (although, I personally disagree with the behavior illustrated
above). Going to mention this at the Keystone meeting today.
** Changed in: keystone
Status: New => Opinion
--
You received this bug notification beca
Closing this because it's not a bug (there's nothing to reproduce), but
subscribing Marek and Steve who should be able to help you out.
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscr
** Also affects: openstack-api-site
Importance: Undecided
Status: New
** Tags added: identity-api
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1334368
Title:
HEAD and GET i
** Changed in: keystone/icehouse
Importance: Undecided => Medium
** Also affects: keystone/grizzly
Importance: Undecided
Status: New
** Changed in: keystone/grizzly
Status: New => Fix Committed
** Changed in: keystone/grizzly
Importance: Undecided => Medium
** Changed in:
I agree, the documentation should be fixed for this.
** Tags added: identity-api
** Project changed: keystone => openstack-api-site
** Changed in: openstack-api-site
Status: New => Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
+1 for documenting the behavior, along with pretty much everything else
in keystoneclient.common.cms
** Project changed: keystone => python-keystoneclient
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.laun
*** This bug is a duplicate of bug 967832 ***
https://bugs.launchpad.net/bugs/967832
** This bug has been marked a duplicate of bug 967832
Resources owned by a project/tenant are not cleaned up after that project is
deleted from keystone
--
You received this bug notification because you
The functional tests here exercise the SQL backend, which is the only
backend we have:
https://github.com/openstack/keystone/blob/master/keystone/tests/test_v3_credential.py
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Y
Comparing just the method difference with curl, I'm not able to
reproduce this. Further, this behavior matches our understanding of
HEAD. The non-zero Content-Length basically indicates to the client how
large the response body would be in a normal GET request.
$ curl http://localhost:35357/v3/gro
I'm going to ignore the mentions of "firstname" and "lastname", since
the patch above ignores them as well.
Up until now, a user's email address has been considered metadata on the
user that Keystone itself makes no guarantees or assumptions about. If
email is to be a first class attribute, I'd li
Actually, I totally overlooked that the request was in the logs, to POST
/v2.0/tokens. There should not be an X-Auth-Token in a request to POST
/v2.0/tokens anyway, so that's completely normal. The rest of the logs
in the problem description are also completely normal, so far as I can
tell.
Withou
There's not a single ERROR level log there from Keystone - this looks to
be coming from apache's log config in devstack?
** Project changed: keystone => devstack
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bu
** Also affects: keystone/icehouse
Importance: Undecided
Status: New
** Changed in: keystone/icehouse
Status: New => In Progress
** Changed in: keystone/icehouse
Importance: Undecided => Medium
** Changed in: keystone
Importance: Undecided => Medium
** Changed in: keyston
This looks like it's an issue between devstack and openstackclient. This
was filed months ago though, is it still an issue?
** Project changed: keystone => devstack
** Changed in: devstack
Status: New => Incomplete
** Also affects: python-openstackclient
Importance: Undecided
St
** Changed in: keystone
Status: Incomplete => 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/1349792
Title:
nova-client return Unauthorized (HTTP 401) when provider is
https://review.openstack.org/#/c/108406/
** Also affects: keystone
Importance: Undecided
Status: New
** Changed in: keystone
Status: New => Triaged
** Changed in: keystone
Importance: Undecided => Medium
** Changed in: keystone
Status: Triaged => Fix Committed
** Cha
This must have been fixed elsewhere.
** Changed in: devstack
Status: New => Invalid
** 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://bugs.launchp
I'd say this is Won't Fix for v2.0. You can use custom logging levels in
eventlet.wsgi.server to suppress this class of logs altogether, but our
solution to the "tokens in URLs" problem was solved by introducing v3
which does not do that - we can't change the v2 API, and I'm not sure
it's a good id
I'm not sure if Keystone or Horizon is at fault here, so I've added both
as Incomplete.
The user may have been created successfully, but keystone will also
attempt to assign the _member_ role to the user in the user's default
tenant (the user.tenant_id attribute in v2, or user.default_project_id
i
** No longer affects: keystone
** Changed in: keystonemiddleware
Importance: Undecided => Wishlist
** Changed in: keystonemiddleware
Status: New => Triaged
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https
fault token provider for Juno.
** Affects: keystone
Importance: Wishlist
Assignee: Dolph Mathews (dolph)
Status: 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/13
** 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/1346210
Title:
keystone v2.0 API docs reported with invalid information
Status in Open
** Changed in: python-keystoneclient
Milestone: None => 0.10.1
** 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.
as compared to what we're producing today:
{"key":"value"}
... as compared to all unnecessary whitespace removed:
{"key":"value"}
This optimization would save us a few bytes in both PKI and PKIZ tokens.
** Affects: keystone
Importance: Wish
** Also affects: keystone/havana
Importance: Undecided
Status: New
** Tags removed: activedirectory havana-backport-potential
** Tags added: ldap
** Changed in: keystone/havana
Status: New => In Progress
** Changed in: keystone/havana
Assignee: (unassigned) => Adam Young (a
** 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/1273988
Title:
keystoneclient requires --pass to create
Public bug reported:
A transient ERROR from a tempest run:
2014-07-07 04:48:43.757 ERROR nova.api.ec2 [req-6705e757-dc7c-4d8c-9b0d-
f0a4e2ea363c EC2VolumesTest-1498681827 EC2VolumesTest-1461531536]
Unexpected InvalidInput raised: Invalid input received: Invalid volume:
Volume status must be avail
Public bug reported:
In a tempest run, I got a:
BuildErrorException: Server cb9b9996-13dd-4f95-9e54-53598723f695
failed to build and is in ERROR status
Which appears to have been caused by this from TRACE
nova.compute.manager:
Traceback (most recent call last):
File "/opt/stack/new/nova/nov
Added keystoneclient so we can have it emit a deprecation warning on
startup.
** Also affects: python-keystoneclient
Importance: Undecided
Status: New
** Changed in: python-keystoneclient
Assignee: (unassigned) => Dolph Mathews (dolph)
** Changed in: python-keystonecli
** Changed in: keystone
Status: In Progress => 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/1079154
Title:
limit users not working
Status in OpenStack Identity (Keys
** Changed in: keystone
Status: Triaged => 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/1188202
Title:
add_user_to_group should return 409 if conflict
Status in Open
** Changed in: keystone
Assignee: Dolph Mathews (dolph) => (unassigned)
** Changed in: keystone
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.ne
This is by design in v2 - that password update call is intended for
administrators. In v3, we support a self-service password change that
requires the user's existing password:
https://github.com/openstack/identity-api/blob/master/v3/src/markdown
/identity-api-v3.md#change-user-password-post-use
This is by design. Project, user and group collections are owned by the
domain, and therefore the policy requires domain-level authorization to
administer those collections.
** Changed in: keystone
Status: In Progress => Invalid
--
You received this bug notification because you are a memb
It looks like swifts middleware could be moved to oslo, as there's
nothing swift-specific about it. There's nothing stopping you from
deploying that middleware in front of Keystone or swift, regardless of
whether it lives in oslo or swift.
** Description changed:
Would be useful for keystone to
Addressed by https://review.openstack.org/#/c/103888/
** Project changed: keystone => openstack-api-site
** Changed in: openstack-api-site
Status: New => Confirmed
** Changed in: openstack-api-site
Status: Confirmed => In Progress
--
You received this bug notification because you
Reverting the above API docs in https://review.openstack.org/#/c/103986/
(approved, but blocked by a gate bug atm) which will render this
invalid.
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, whic
It looks like this issue specifically affects havana, as Icehouse and
master both generate the sample configuration dynamically. Given that
keystone.conf.sample represents an important source of documentation,
I'd love to see a fix included in stable/havana.
** Also affects: keystone/havana
Imp
** 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/1334739
Title:
A bug for test(ignore it)
Status in OpenStack Identity (Keystone):
** Changed in: keystonemiddleware
Assignee: (unassigned) => Brant Knudson (blk-u)
** Changed in: keystonemiddleware
Status: New => Triaged
** No longer affects: python-keystoneclient
** Changed in: keystonemiddleware
Importance: Undecided => Wishlist
** Changed in: keystone
Im
** Changed in: keystonemiddleware
Importance: Undecided => Wishlist
** Changed in: keystonemiddleware
Status: New => Triaged
** No longer affects: python-keystoneclient
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Ke
Closes-Bug should actually work, but unfortunately the bug was targeted
at keystone rather than python-keystoneclient.
** Project changed: keystone => python-keystoneclient
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
Happy to see this improved, but we don't require a bug to track the
work. Thanks!
** 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/1332
Public bug reported:
This appeared as a transient failure in a doc change. I suspect the test
shouldn't bother asserting the order of the results, only that the
expected values appear in the list.
==
FAIL:
keystone.tests.test_v2
Public bug reported:
In console.html, I got:
Log: n-api-meta not allowed to have ERRORS or TRACES
And in logs/screen-n-api-meta.txt.gz:
2014-06-18 02:51:38.284 DEBUG nova.openstack.common.policy
[req-fe1ab254-c41e-41b0-8070-1b1bcc8ca41f None None] Rule
network:get_fixed_ip_by_address will be
** Changed in: keystone
Status: Incomplete => Invalid
** Changed in: pbr
Status: Incomplete => New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1330771
Title:
pbr as ru
This shouldn't affect keystone, as we neither specify nor implement this
resource.
The apparently equivalent call that we do implement is:
GET /v3/role_assignments?user.id={user_id}
https://github.com/openstack/identity-api/blob/master/v3/src/markdown
/identity-api-v3.md#list-effective-role-as
Is this an issue with PBR or how we're using it?
** Changed in: keystone
Status: New => Incomplete
** Also affects: pbr
Importance: Undecided
Status: New
** Changed in: pbr
Status: New => Incomplete
--
You received this bug notification because you are a member of Yahoo
** Tags removed: documentation
** Tags added: identity-api
** Project changed: keystone => openstack-api-site
** Changed in: openstack-api-site
Status: New => Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keyst
** Project changed: keystone => python-keystoneclient
** Tags added: user-experience
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1328359
Title:
keystone uses incorrect OS_AUTH_URL
If you find that it's not addressed in 0.9.0, please comment here so we
can re-open this. Thanks!
** Changed in: keystone
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.
That's originally by design, but I agree with the notion that users
should be able to delete their own tokens, even though it's
traditionally an administrative function (I see it as "logging out").
** Changed in: keystone
Importance: Undecided => Wishlist
** Changed in: keystone
Status:
The policy rules you're looking at apply to the v3 API, but the calls to
assert_admin() you've cited are part of the v2 API. The v3 API supports
fairly granular policy enforcement, but the v2 API is generally binary
(you're either "admin" or not, and all that policy does is define what
"admin" mean
** Changed in: keystone
Importance: Undecided => Critical
** Also affects: python-keystoneclient
Importance: Undecided
Status: New
** Changed in: python-keystoneclient
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Yahoo!
Engi
** 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.launchpad.net/bugs/1326811
Title:
Client failing with six =>1.6 error
Status in OpenSt
Public bug reported:
The v3 API specifies that endpoints appearing in the service catalog
should have an ID [1].
This patch finally introduced v3 support for the KVS and templated
backends, but unfortunately does not address the lack of endpoint IDs.
Even in the case of the KVS and templated impl
** Also affects: openstack-manuals
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1314125
Title:
No errors when creating keystone tables when
** Also affects: keystone/icehouse
Importance: Undecided
Status: New
** Changed in: keystone/icehouse
Importance: Undecided => Medium
** Changed in: keystone/icehouse
Assignee: (unassigned) => Emilien Macchi (emilienm)
** Changed in: keystone/icehouse
Status: New => In P
Removed python-keystoneclient from this bug due to launchpad issues -
fix released in python-keystoneclient 0.9.0.
** No longer affects: python-keystoneclient
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.l
** 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/1255321
Title:
v3 token requests result in 500 error whe
** 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/1174499
Title:
Keystone token hashing is MD5
Status in
** 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/1250617
Title:
Limited use trusts
Status in OpenStack I
** 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/1312858
Title:
Keystone + Devstack fail when KEYSTONE_TO
** Also affects: keystone/icehouse
Importance: Undecided
Status: New
** Changed in: keystone/icehouse
Status: New => Triaged
** Changed in: keystone/icehouse
Importance: Undecided => Low
--
You received this bug notification because you are a member of Yahoo!
Engineering Tea
IIRC, this was actually being caused by an out-of-tree patch being
carried by Debian. Please re-open if I'm mistaken.
** Changed in: keystone
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Key
++
** Changed in: keystone
Status: Triaged => 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/1065233
Title:
Roles in XML response of v2 Validate Token Call not inline
We now have containers for users (domains and external IdPs), which I
think satisfies the requirement for certain users to carry a special
designation (they could be owned by a service domain, for example).
** Changed in: keystone
Importance: Medium => Wishlist
** Changed in: keystone
S
Most of the issues described here are resolved by following the dev docs
[1] instead of the "install from source" docs. I think it would be best
to merge these two documents, or just outright nuke the "install from
packaging" [2] page since that should really be documented downstream,
or in opensta
Thanks, treinish!
** Changed in: keystone
Status: Incomplete => 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/1321797
Title:
Tempest fails on backports to Icehouse
Sta
I believe I saw this issue being discussed as either a tempest or
grenade issue, but I'm unable to find the bug report... filing against
those projects in hopes of seeing this marked as a dupe :) Otherwise,
poke me if I'm mistaken.
** Also affects: tempest
Importance: Undecided
Status: N
avior.
** Affects: keystone
Importance: Low
Assignee: Dolph Mathews (dolph)
Status: Triaged
** Tags: user-experience
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1322187
** Project changed: keystone => keystone (Ubuntu)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1319425
Title:
keystone link not created in /etc/init.d
Status in “keystone” package in
201 - 300 of 619 matches
Mail list logo
