The core issue described by the bug is one of user experience, so I
think the direction is certainly valid. The response should still be a
500, as well. However, we're not providing adequate feedback to the
deployer about what went wrong, and perhaps providing too much
information to the API user (who *may* not be the deployer).
** Changed in: keystone
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1177623
Title:
keystone reports internal error when policy.json is broken
Status in OpenStack Identity (Keystone):
Confirmed
Bug description:
if policy.json is broken, when using keystone apis, will return HTTP
500 (internal error).
For better user experience, we need to provide:
1). a better response for use to explain what had happend
and
2). a default policy list to use in case the policy.json is broken.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1177623/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
