i'd prefer to fix this on the server side, adding more fields on the
server side would be much faster, and save the client from doing a bunch
of look ups
** Changed in: python-openstackclient
Importance: Undecided => Medium
** Also affects: keystone
Importance: Undecided
Status: New
Morgan, Gilles and I spoke about this on IRC. I think we agreed that
making the columns in the trust database have a unique constraint is the
way to go. So if two requests came to create trusts with the same
trustor/trustee/roles/expiration/scope/impersonation, then the second
would bring up an exc
Public bug reported:
The docs in this section: http://docs.openstack.org/developer/keystone
/http-api.html#i-am-a-deployer
reference an editable section in keystone-paste.ini ([app:service_v3]).
this section is now managed by entry points in setup.cfg
** Affects: keystone
Importance: Undec
acked and
documented.
** Affects: keystone
Importance: Undecided
Assignee: Steve Martinelli (stevemar)
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net
if this is a keystone bug, which by the sound of it, isn't likely, we
would need some logs
** Also affects: horizon
Importance: Undecided
Status: New
** Changed in: keystone
Status: New => Incomplete
--
You received this bug notification because you are a member of Yahoo!
Engin
keystone patch here: https://review.openstack.org/#/c/240762/
** Also affects: keystone
Importance: Undecided
Status: New
** Changed in: keystone
Status: New => In Progress
** Changed in: keystone
Importance: Undecided => Low
** Changed in: keystone
Assignee: (unassigne
The content here: http://specs.openstack.org/openstack/keystone-
specs/api/v3/identity-api-v3.html is considered the source of truth.
The content under http://developer.openstack.org/api-ref-
identity-v3.html is known to be out of date, much more than just
/v3/auth/tokens is out of date, that is a
what are you adding this? it's not in the schema [0] or saved in the
backend [1]
0 - https://github.com/openstack/keystone/blob/master/keystone/policy/schema.py
1 -
https://github.com/openstack/keystone/blob/master/keystone/policy/backends/sql.py
i'm not understanding how a project is associated
Looks like the examples under /policies here: are incorrect
http://developer.openstack.org/api-ref-identity-v3.html
I suggest looking at: http://specs.openstack.org/openstack/keystone-
specs/api/v3/identity-api-v3.html
Feel free to fix the inconsistencies in the api-site, they are here:
https://g
Public bug reported:
With a current devstack setup, in local_settings.py, change
'OPENSTACK_KEYSTONE_URL' to end in /v3 instead of /v2.0, this should
trigger v3 auth flows.
But instead I can't log in at all, enabling debug, i see the following:
2015-11-10 16:17:53.240277 DEBUG:keystoneclient.aut
I had to add "OPENSTACK_API_VERSIONS", and the 'identity' block to get
this to work.
** Changed in: horizon
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.
?? how is this a keystone issue?
are you referring to some online document?
** Also affects: cinder
Importance: Undecided
Status: New
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
until this is brought up as a real issue in a real environment and not a
script that creates churn for the sake of churn, we won't be fixing it
in keystone.
** Changed in: keystone
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
E
Bugs should be reserved for issues that end users are hitting with the
current code base. If there is a missing test, just add it to the code
base.
Unless adding a test is showing a bug in the code, then there is no need
to create a bug.
I'm going to mark the bug as invalid, but I'd be more than
Public bug reported:
keystone currently support a lot of event notifications, just see
http://docs.openstack.org/developer/keystone/event_notifications.html
It would be nice if there was a configuration option to allow users to
opt-out of notifications they didn't care about.
This could be as si
*** This bug is a duplicate of bug 1475831 ***
https://bugs.launchpad.net/bugs/1475831
** This bug has been marked a duplicate of bug 1475831
Some compute quotas are not being set
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribe
lin, looks like there wasn't really an issue, had to sync up
requirements or install parsley. marking as invalid
** 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 Ident
Public bug reported:
With the LDAP backend for assignment and resource being potentially
removed in Mitaka, we probably don't want the role backend to support
LDAP either. It currently does and is not marked for deprecation either
https://github.com/openstack/keystone/blob/master/keystone/assignme
bug submitter claims it's not a bug, good enough for me
** 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 Identity (keystone).
https://bugs.launchpad.net/bugs/1520085
CLI for keystoneclient has been deprecated, assigning the bug to
openstackclient.
marking as won't fix for keystoneclient
** Also affects: python-openstackclient
Importance: Undecided
Status: New
** Summary changed:
- keystone user-password-update also accept blank password.
+ passwo
finding the service catalog through python bindings is available now,
following sean's comment i don't believe this is an issue any longer. if
it is, please re-open
** Changed in: python-keystoneclient
Status: Confirmed => Invalid
--
You received this bug notification because you are a me
reading the backlog, this seems fixed on the keystoneclient side,
marking this as fix released
** Changed in: python-keystoneclient
Importance: Undecided => Medium
** Changed in: python-keystoneclient
Status: Confirmed => Fix Released
--
You received this bug notification because you
we will not be pursuing any more PKI related work, as of Mitaka the
keystone team has deprecated PKI tokens.
** Changed in: python-keystoneclient
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
same reasoning for keystoneclient issue, won't fix.
** Changed in: python-keystoneclient
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad
there doesn't seem to be an issue with keystoneclient?
** Changed in: python-keystoneclient
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.
i am very unclear as to what the bug is here (from a keystone and
keystoneclient perspective). we do not support or advertise the user of
versionId, versionList and versionInfo in our APIs. if you are using a
third party library, file a bug with them.
** Changed in: python-keystoneclient
St
so the CLI still defaults to 'regionOne', but it's deprecated in favor
of openstackclient.
openstackclient, and the python bindings in keystoneclient do not
default region name to anything and let the server handle the default
name (RegionOne), so there is nothing left to fix here, we won't be
fix
use https://blueprints.launchpad.net/keystone/+spec/removed-as-of-mitaka
** 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 Identity (keystone).
https://bugs.launchpad.n
ksm is released for kilo, marking this as fix-released for
keystonemiddleware
** Changed in: keystonemiddleware
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/
marking as invalid for ksm, we have python-memcached>=1.5.6 as of mitaka
** Changed in: keystonemiddleware
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.l
we've been setting the default volume api version 2 since 1.7.0, we're
at 1.9.0 now. marking this as fix released for openstackclient, see
commit: https://github.com/openstack/python-
openstackclient/commit/f14251669f96d6010581702417828f4380144aa2
** Changed in: python-openstackclient
Statu
** Changed in: python-openstackclient
Status: New => Incomplete
** Changed in: python-openstackclient
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/b
*** This bug is a duplicate of bug 1391116 ***
https://bugs.launchpad.net/bugs/1391116
** This bug has been marked a duplicate of bug 1391116
password prompts should check for empty string
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
we don't use WADLs for v3, we settled on RST and publish here:
http://specs.openstack.org/openstack/keystone-specs/api/v3/identity-
api-v3.html
** Changed in: keystone
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, w
init scripts are not keystone's responsibility, simply because they will
be different for each deployment. this is a configuration management
issue and folks should use tools they want and prefer rather than
something the keystone team bakes up.
** Changed in: keystone
Status: Triaged => Wo
i think the testing here is sufficient
https://github.com/openstack/keystone/blob/5de11025f45ca10d2b02b70234c1305fae91766c/keystone/tests/unit/test_backend.py#L1101-L1148
and covers a lot of what was in the abandoned patch
** Changed in: keystone
Status: In Progress => Invalid
--
You rece
the json schema should address this now, as it's a required field:
https://github.com/openstack/keystone/blob/master/keystone/catalog/schema.py
** Changed in: keystone
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, whi
we are going to deprecate support for create/update/delete for users and
groups in LDAP since it is a very uncommon use case. marking as won't
fix.
** Changed in: keystone
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Te
we will be deprecating support for user and group create/delete/update
in mitaka, marking this as won't fix as it is not a security issue and
does not align with project plans
** Changed in: keystone
Status: In Progress => Won't Fix
--
You received this bug notification because you are a
we'll be deprecating all LDAP backends that aren't identity
** Changed in: keystone
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/b
write support for the identity ldap backend is being deprecated
** 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 OpenStack Identity (keystone).
https://bugs.launchpad.ne
im marking keystone as invalid for now since this seems like it's fuel
related, update if i'm incorrect
** 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 Identity (keys
role assignments in ldap has been deprecated for at least one release,
this will not be fixed
** 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 OpenStack Identity (keystone
use openstackclient for this, the use of `keystone' has been deprecated,
i'm surprised you are not receiving error/deprecation warnings when
using that command.
in openstackclient, it would be `openstack user create xyz123` with
--enable and --disable being FLAGS and not options like in
keystonecl
the patches associated with this bug are abandoned and as written in #2,
install_venv.py is gone from master
** 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 OpenStack I
lots of back and forth on this one, i think we agreed that it's fine on
specs.openstack.org/keystone
** 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 OpenStack Identity
it seems like nova has removed the mechanism to register and unregister
models, as have other projects, like congress:
https://github.com/openstack/congress/commit/63976719d6cfdc8d5518c7378d52d30c739b8ebd
by the looks of it, only glance supports it:
http://hound.openstack.org/?q=register_model&i=n
sorry dolph, as you have told me many times, the admin token itself
carries no authorization. if you disagree open a bug against
openstackclient to have this as a client specific feature, keystone
server shouldn't change the way it's handled
** Changed in: keystone
Status: Confirmed => Won'
this is a blueprint/spec
** Changed in: keystone
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1070637
Title:
create tokens scop
we no longer have images in our docs
** Changed in: keystone
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1121648
Title:
conv
this should be reproposed as a blueprint/spec, and since it's been ~2
years with no comments, i'm going to assume it's OK to mark this as
won't fix since no one wants to pick up the work
** Changed in: keystone
Status: Triaged => Won't Fix
--
You received this bug notification because you
this is covered by revocation events and audit ids that have been around
for a few releases
** Changed in: keystone
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keyst
*** This bug is a duplicate of bug 1332666 ***
https://bugs.launchpad.net/bugs/1332666
** This bug has been marked a duplicate of bug 1332666
Poor performance on delete_tokens due to missing indexes
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
marking keystone as invalid since we have a duplicate bug here: 1519580
and we now use JSON schema validation for our v3 calls
** Changed in: keystone
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribe
this was fixed by the patch in #6
** Changed in: keystone
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1387379
Title:
sounds like this was user error in the way auth_version was being passed
in, doesn't affect keystone
** 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 Identity (keyston
there is no obvious bug here, if it is a refactor, simply propose the
patch
** Changed in: keystone
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.laun
unassigning due to inactivity and failing patch sets, also this doesn't
affect keystoneclient
** Changed in: python-keystoneclient
Status: Triaged => Invalid
** Changed in: keystone
Status: In Progress => Confirmed
** Changed in: keystone
Assignee: Marek Denis (marek-denis) =>
use bp https://blueprints.launchpad.net/keystone/+spec/deprecated-as-of-
mitaka to track 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 OpenStack Identity (keystone).
htt
different users with the same name should be in different domains.
** 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 Identity (keystone).
https://bugs.launchpad.net/bug
Public bug reported:
With the latest pycadf release (2.0.0), there is a more strict
validation on the ID fields of various CADF resources, in this case, the
initiator is failing to validate some keystone user IDs.
This only happens when multi-domains are configured. An ID for a user in
a multi-do
** Changed in: python-keystoneclient
Status: Fix Committed => Fix Released
** Changed in: python-keystoneclient-kerberos
Status: Fix Committed => Fix Released
** Changed in: keystonemiddleware
Status: Fix Committed => Fix Released
** Changed in: keystone
Status: In Pr
Public bug reported:
Currently, when a federated user gets a token, it has an OS-FEDERATION
section under 'user', which contains information about the idp and
protocol.
However when the same user uses the unscoped token to get a scoped
token, we should put the same information in there as well. T
Public bug reported:
Currently, when a federated user gets a token, it has an OS-FEDERATION
section under 'user', which contains information about the idp and
protocol.
However when the same user uses the unscoped token to get a scoped
token, we should put the same information in there as well. T
re as well. This will
help support revocation events for federated tokens, i.e. revoking all
tokens based on IDP id.
** Affects: keystone
Importance: Undecided
Assignee: Steve Martinelli (stevemar)
Status: In Progress
--
You received this bug notification because you are a membe
Importance: Undecided
Assignee: Steve Martinelli (stevemar)
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1352115
Title:
stop spamming cadf event authn
We want to encourage the use of tox rather than run_tests, can you try
running tox with -e debug
`tox -e debug` - it should enable debugging.
** Changed in: keystone
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team
This was fixed when PKIZ was added to Keystone:
https://github.com/openstack/keystone/commit/063070f21ffc3345e2b25904ff4a1ae89f539c32
** Changed in: keystone
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
>From what I can tell this isn't a Keystone bug, but I appreciate the
heads up. If I'm wrong, let me know.
** 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://bug
d') and context['is_admin']):
raise exception.Forbidden()
There are two checks for matching trustor, when one should be trustee.
Also the admin check is pointless, since it should be just trustee or trustor.
** Affects: keystone
Importance: Undecided
Assign
Public bug reported:
Given the outcome of: https://bugs.launchpad.net/keystone/+bug/1259440
And a recent colleague asking why he can't use the admin token to get a list of
projects we should address the misconception surrounding this part of the
keystone.conf file.
Currently, it reads:
[DEFAULT
Public bug reported:
According to the API Spec, we should be able to create a region with a specific
id:
https://github.com/openstack/identity-api/blob/master/openstack-identity-api/v3/src/markdown/identity-api-v3.md#create-region-with-specific-id-put-regionsuser_defined_region_id
I don't believ
please don't open bugs for these issues, just submit a patch. there's no
real end user issue here.
** 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 OpenStack Identity (k
** Changed in: keystone
Status: Triaged => Invalid
** Changed in: keystone
Milestone: ocata-1 => None
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/162813
** Changed in: python-openstackclient
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1460492
Title:
List credentials by type
** Changed in: keystone/mitaka
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1592169
Title:
cached tokens break Libert
Thanks for the quick analysis here Ben. Looking at newton and future
releases, if you are using the "keystone-manage bootstrap" option to
setup keystone, then the domain ID won't be "default" it'll be some
UUID. Your best bet going forward is to use the domain name only, it'll
always be "Default" (
this is as-designed. no delete operations give feedback. just as in
linux if something does not give you an error, you can assume it
occurred just fine.
https://www.quora.com/What-is-the-appropriate-HTTP-response-code-to-a
-successful-DELETE-request
** Changed in: keystone
Status: New => I
Not a keystone bug, what tool did you use to perform the operation?
** 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 Identity (keystone).
https://bugs.launchpad.net/bu
Public bug reported:
Include https://github.com/openstack/keystone-specs/blob/master/attic/v3
/identity-api-v3.rst in the file
https://raw.githubusercontent.com/openstack/keystone/master/api-
ref/source/v3/index.rst
3.7 == Newton, work your way back from there.
-
** Also affects: ubuntu
Importance: Undecided
Status: New
** No longer affects: ubuntu
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1637850
Title:
newt
In this case, the API needs to be updated, it should include the
"unscoped" option: https://github.com/openstack/keystone/blob/master
/api-ref/source/v3/authenticate-v3.inc
The issue here is that we moved our APIs from one repo to another and
some content went missing in the transition.
Informati
Patch https://review.openstack.org/#/c/389783/ closes the bug from the
keystone side
** Also affects: keystone
Importance: Undecided
Status: New
** Changed in: keystone
Status: New => In Progress
** Changed in: keystone
Importance: Undecided => High
** Changed in: keystone
** Also affects: keystone/newton
Importance: Undecided
Status: New
** Changed in: keystone/newton
Status: New => In Progress
** Changed in: keystone/newton
Importance: Undecided => High
** Changed in: keystone/newton
Assignee: (unassigned) => Adam Young (ayoung)
--
You
This is an implementation detail and we won't be fixing it in Keystone.
There's no gain as far as I can tell.
** Changed in: keystone
Status: New => Invalid
** No longer affects: keystone
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
** Changed in: keystone
Status: In Progress => Fix Released
** Also affects: keystone/newton
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https:/
Hi Scott, I manage the keystone queue for launchpad, it's meant for
keystone bugs, the issue you're having (IIUC) is related to the RPM
package. I don't want to simply mark the bug as invalid and leave you in
a lurch. So I'll provide some pointers:
The red hat published install guide can be seen h
No movement in months, there is no direct user impact here so I'm
marking as invalid.
** 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 OpenStack Identity (keystone).
htt
Public bug reported:
Currently, the user's name (and domain name), their roles, the project
they authenticated with (and project's domain name) are supplied in the
k2k assertion that keystone generates.
There has been a request that the user's groups also be included in the
assertion.
** Affects
Public bug reported:
There are no developer docs on how to create a new doctor check, or how
the existing ones work. They should be added to a new section in the
"developer docs" here: http://docs.openstack.org/developer/keystone
/#developers-documentation
** Affects: keystone
Importance: Me
Public bug reported:
there are no tests for any keystone-manage doctor commands. they should
be created here:
https://github.com/openstack/keystone/blob/master/keystone/tests/unit/test_cli.py
** Affects: keystone
Importance: Low
Status: Triaged
** Tags: test-improvement
--
You r
Public bug reported:
Currently, shadow users are created for users that log in through
federation. New "local_user" accounts are created with a new UUID.
Rather than creating a new UUID, we should re-use the mapping_id backend
that was employed with LDAP users.
** Affects: keystone
Importanc
Public bug reported:
As noted in the bug title, this is a cumbersome process, a user should
be able to reset their password if it expired. (and potentially if
locked out -- that's up for debate).
** Affects: keystone
Importance: Medium
Status: New
** Tags: pci
--
You received th
Public bug reported:
The main idea behind the user ID blacklist for PCI was to allow service
accounts to not have to change their password. As noted in [1], a by-
product of any PCI implementation is a vulnerability to a DoS (a
malicious user attempting to login X times and locking out a user). Th
Public bug reported:
When [1] merged, it fixed many caching issues and bug, but created
another. The region invalidation should be wrapped to the local context.
Patch: https://review.openstack.org/#/c/380376/
** Affects: keystone
Importance: High
Assignee: Boris Bobrov (bbobrov)
Public bug reported:
The healthcheck middleware is published by oslo, used in glance and
magnum, and one less thing for deployers to add to keystone. Let's add
it in.
Patch: https://review.openstack.org/#/c/387731/
** Affects: keystone
Importance: Medium
Assignee: Jesse Keating (jesse-
Public bug reported:
The current default notification format is the home-brewed openstack-
styled format, that provides minimal information about the user. For a
few releases now, all new notifications have adhered to the CADF format.
We should switch over to the CADF format, which provides compat
** Changed in: keystone/newton
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1621200
Title:
password created_at does n
Public bug reported:
keystone provides a configuration option to "pre-cache" a token, it is
cached upon issue. In the Newton release this was disabled by default,
we should enable it in Ocata.
** Affects: keystone
Importance: Medium
Assignee: Matt Fischer (mfisch)
Status: In Pr
Public bug reported:
The caching document in the admin guide is sorely out of date by at
least 2 releases. Update it to reflect current status.
http://docs.openstack.org/admin-guide/identity-caching-layer.html
** Affects: keystone
Importance: Low
Assignee: Eric Brown (ericwb)
S
1 - 100 of 501 matches
Mail list logo
