yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #77748
[Bug 1817313] Re: RBAC Enforcer Programming Error raised for malformed federation protocol request
Reviewed: https://review.openstack.org/648241
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=9717f0c12f225a70fcecebcfcfc6dd4f1e248b28
Submitter: Zuul
Branch: master
commit 9717f0c12f225a70fcecebcfcfc6dd4f1e248b28
Author: Morgan Fainberg <morgan.fainberg@xxxxxxxxx>
Date: Wed Mar 27 13:49:39 2019 -0700
Raise METHOD NOT ALLOWED instead of 500 error on protocol CRUD
Raise METHOD NOT ALLOWED for OS-Federation protocols creation
if the protocol_id is not in the URL. The corrective action was to split
the LIST from CRUD resources so that the routing regexes can work as
expected.
Change-Id: I063e3afa1ef8dbf957d62fb4d44dac0f0860ec94
closes-bug: #1817313
** 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/1817313
Title:
RBAC Enforcer Programming Error raised for malformed federation
protocol request
Status in OpenStack Identity (keystone):
Fix Released
Bug description:
On devstack, I mistakenly tried to create a federation protocol
without providing its name in the request path:
curl -H "x-auth-token: $token" -H "content-type: application/json"
http://localhost/identity/v3/OS-
FEDERATION/identity_providers/myidp/protocols -X PUT -d '{"protocol":
{"mapping_id": "myidp_mapping"}}'
This caused the RBACEnforcer programming error to be raised:
http://paste.openstack.org/show/745721/
Also, the error message spells RBACEnforcer incorrectly.
Expected behavior: this should result in a 404, not a 500.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1817313/+subscriptions
References